mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-22 17:22:47 +00:00
* fix(plugins): keep React out of the server plugin host * fix(plugins): align SDK guidance and tests with runtime boundaries * fix(plugin): loosen the react peer to ~19.1.0 The plugin SDK pins its react peer to exactly 19.1.0, and that pin is what a downstream `npm i -g @getpaseo/cli` resolves against. So every user ends up with react 19.1.0 in their global node_modules, where corporate dependency scanners flag it: the CVE-2025-55182 advisory range covers 19.1.0 even though the vulnerability itself lives in react-server-dom-webpack/-parcel/-turbopack, none of which the CLI installs. The user is then left hand-patching node_modules or uninstalling Paseo. Widening the peer to ~19.1.0 lets a downstream install pick the latest 19.1.x patch (19.1.9 today) while this repo stays on 19.1.0, which the root override still pins. Keeping the repo itself on 19.1.0 is deliberate. react-native 0.81.5 embeds a 19.1.0 Paper renderer that hard-throws "Incompatible React versions" on any exact mismatch, and it is reachable from Fabric builds too: RendererImplementation.js requires the Paper shim unconditionally in findNodeHandle, unstable_batchedUpdates, sendAccessibilityEvent and three other entry points, and react-native-gesture-handler re-exports findNodeHandle. Bumping the app's react is therefore not safe until react-native moves. The published CLI tree contains no react-native, so downstream installs are not subject to that constraint. Supersedes the earlier 19.1.5/19.1.9 version-bump approach on this branch, which would have broken the mobile app. * Enforce example import ownership including client types * Update Nix dependency hash for plugin peer metadata * Group plugin APIs under client and server entry trees * Resolve plugin type dependencies through declarations * Validate declarations for implicit plugin type imports * Preserve optional imports and validate declaration references * Refresh Nix hash for plugin declaration resolver * Canonicalize plugin paths consistently on Windows * Normalize plugin ownership paths across resolver boundaries --------- Co-authored-by: liujin0506 <liujin0506@qq.com> Co-authored-by: Mohamed Boudra <boudra.moha@gmail.com>
67 lines
2.2 KiB
TypeScript
67 lines
2.2 KiB
TypeScript
import type { PluginTimelineItemProps } from "@getpaseo/plugin/client";
|
|
import { useMemo } from "react";
|
|
import { Text, View } from "react-native";
|
|
import type { z } from "zod";
|
|
import { piTaskListSchema } from "../shared/pi-tasks";
|
|
|
|
type TaskListData = z.output<typeof piTaskListSchema>;
|
|
|
|
const taskMarker = {
|
|
completed: "✓",
|
|
in_progress: "◐",
|
|
pending: "○",
|
|
} as const;
|
|
|
|
export function PiTaskList({ item, theme }: PluginTimelineItemProps<TaskListData>) {
|
|
const completed = item.data.tasks.filter((task) => task.status === "completed").length;
|
|
const styles = useMemo(
|
|
() => ({
|
|
card: {
|
|
gap: 8,
|
|
borderWidth: 1,
|
|
borderColor: theme.colors.border,
|
|
borderRadius: 10,
|
|
padding: 12,
|
|
backgroundColor: theme.colors.surface1,
|
|
},
|
|
header: {
|
|
flexDirection: "row" as const,
|
|
justifyContent: "space-between" as const,
|
|
},
|
|
title: { color: theme.colors.foreground, fontWeight: "600" as const },
|
|
progress: { color: theme.colors.foregroundMuted },
|
|
task: { flexDirection: "row" as const, gap: 8 },
|
|
completed: { color: theme.colors.statusSuccess },
|
|
inProgress: { color: theme.colors.accent },
|
|
pending: { color: theme.colors.foregroundMuted },
|
|
taskText: { color: theme.colors.foreground, flex: 1 },
|
|
completedText: { color: theme.colors.foregroundMuted, flex: 1 },
|
|
}),
|
|
[theme],
|
|
);
|
|
|
|
return (
|
|
<View style={styles.card}>
|
|
<View style={styles.header}>
|
|
<Text style={styles.title}>Pi tasks</Text>
|
|
<Text style={styles.progress}>
|
|
{completed}/{item.data.tasks.length}
|
|
</Text>
|
|
</View>
|
|
{item.data.tasks.map((task) => {
|
|
let markerStyle = styles.pending;
|
|
if (task.status === "completed") markerStyle = styles.completed;
|
|
if (task.status === "in_progress") markerStyle = styles.inProgress;
|
|
return (
|
|
<View key={task.text} style={styles.task}>
|
|
<Text style={markerStyle}>{taskMarker[task.status]}</Text>
|
|
<Text style={task.status === "completed" ? styles.completedText : styles.taskText}>
|
|
{task.text}
|
|
</Text>
|
|
</View>
|
|
);
|
|
})}
|
|
</View>
|
|
);
|
|
}
|