tben
aebd6b8ccc
There is no public media any more. `/media/public/<id>` served a media row with no session at all, so anyone with the id could read a file. The public/private split is gone: the path is `/media/<id>` (and `/media/<id>/thumbnail`), every request is signed in first, and `grabUserMedia` decides whether the user may see it: their own upload, a bot's or workspace's picture or file they reach, or a file on a task they reach. Anything else is a 404 before a path is built. The `media.is_private` column and the two per-user directories went with it: uploads live in `media/<user_id>/` and there is nothing to pick between. The files browser's media volume is now the viewer's own folder whatever their role. Bots also say which of the two things they mean. A `[file:ID]` ref is a saved file and its chip opens the bytes; a folder is a new `[folder:volume:owner:path]` ref (`src/utils/folder-ref.ts`) whose chip opens the files browser there and downloads nothing. The old `[path:...]` ref and the extension sniffing that guessed file from folder are gone, so `import_file` names the folder holding a file it copied rather than the file itself. The prompts say what the Assistant got wrong: list before importing or saving, one copy per artifact, never split a file into parts unless asked, never claim the store is empty without a fresh list, and never invent a size cap. A re-import now says the path already existed instead of silently overwriting and reporting a fresh copy.
39 lines
1.6 KiB
TypeScript
39 lines
1.6 KiB
TypeScript
import Link from "@moduletrace/twui/layout/Link";
|
|
import Span from "@moduletrace/twui/layout/Span";
|
|
import { FolderOpen } from "lucide-react";
|
|
import { folderRefUrl } from "@/src/utils/folder-ref";
|
|
import { storagePathName, type StorageSpec } from "@/src/utils/storage-volumes";
|
|
|
|
type Props = {
|
|
spec: StorageSpec;
|
|
path: string;
|
|
};
|
|
|
|
/**
|
|
* A folder a bot named in a message (`folderRef`): the name it ends with,
|
|
* linked into the files browser, where the user can look at everything in
|
|
* it. Nothing is downloaded: a folder ref never serves bytes, and this chip
|
|
* never guesses from the name whether it is a file or a folder, because the
|
|
* ref itself already says it is a folder. A file the bot saved is a file
|
|
* ref (`fileRef`) and opens the file instead.
|
|
*
|
|
* Written without a literal ref in this comment on purpose: Tailwind scans
|
|
* every page and partial, reads a bracketed `name:value` as an
|
|
* arbitrary-property utility, and emits it as a real CSS property (esbuild
|
|
* then warns that `file` is not one).
|
|
*/
|
|
export default function FolderRefChip({ spec, path }: Props) {
|
|
const name = storagePathName({ volume: spec.volume, path });
|
|
|
|
return (
|
|
<Link
|
|
href={folderRefUrl({ volume: spec.volume, owner_id: spec.owner_id, path })}
|
|
title={`Open ${path || name} in Files`}
|
|
className="inline-flex h-6 max-w-full gap-1.5 items-center px-1.5 align-middle rounded-default-xs border-0 bg-sunken text-[13px] font-bold leading-4 text-ink hover:opacity-80"
|
|
>
|
|
<FolderOpen size={14} aria-hidden className="shrink-0" />
|
|
<Span className="truncate">{name}</Span>
|
|
</Link>
|
|
);
|
|
}
|