Let a bot's reply link to the files it saved
Both runners now pass the files a run wrote back into the reply, and a computer file ref renders as a chip like a bot file ref does, so a reply can point at what it produced instead of naming a path.
This commit is contained in:
@@ -8,9 +8,11 @@ import {
|
||||
TakeOverRefHrefPrefix,
|
||||
WorkspaceRefHrefPrefix,
|
||||
} from "@/src/utils/link-computer-refs";
|
||||
import { parsePathRefHref } from "@/src/utils/path-ref";
|
||||
import BotRefChip from "./bot-ref-chip";
|
||||
import ComputerRefChip from "./computer-ref-chip";
|
||||
import FileRefChip from "./file-ref-chip";
|
||||
import PathRefChip from "./path-ref-chip";
|
||||
import TakeOverChip from "./take-over-chip";
|
||||
import WorkspaceRefChip from "./workspace-ref-chip";
|
||||
|
||||
@@ -61,6 +63,10 @@ export default function MarkdownLink({ href, children }: ComponentProps<"a">) {
|
||||
if (file_id) return <FileRefChip file_id={file_id} />;
|
||||
}
|
||||
|
||||
const path_ref = parsePathRefHref({ href });
|
||||
|
||||
if (path_ref) return <PathRefChip spec={path_ref.spec} path={path_ref.path} />;
|
||||
|
||||
return (
|
||||
<Link
|
||||
href={href}
|
||||
|
||||
Reference in New Issue
Block a user