pastilhasandClaude Opus 5
9cbbc28c82
it was a permanent line under the controls saying "Saved." — which said nothing, because everything on this screen has been saved, all the time. it looked exactly like feedback, so the one moment it actually meant something was indistinguishable from every moment it did not. now it appears when a save LANDS and clears itself. top-right of the block, beside the title rather than in the flow: it is a remark about the block, not part of what you are doing, and inline it pushes everything below down a line and then pulls it back up — a layout that jumps every time somebody saves. "Not set yet" stays. that IS a state, and it is the one worth knowing; it goes when it stops being true rather than being replaced by a line that never changes. the timer is a ref and is cleared before each new one. without that, saving twice in quick succession leaves the first timeout running and it fires against the second save — the confirmation vanishing a moment after appearing, which reads as the second save failing. Block moved to its own file and each setting now renders its own. the status belongs to the setting that produced it, and lifting one block's timer into the panel would put it in a component with nothing to do with it. that is also what made the top-right slot possible without absolutely positioning anything. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
27 lines
1.0 KiB
TypeScript
27 lines
1.0 KiB
TypeScript
import { RootLocationBlock } from './RootLocationBlock';
|
|
import { DatabaseBlock } from './DatabaseBlock';
|
|
|
|
/**
|
|
* Administration — this plugin's own machinery, not the client's site.
|
|
*
|
|
* A list of blocks, and nothing else. Each one owns its own heading, its own state and its own status
|
|
* message; this file decides only which of them exist and in what order.
|
|
*
|
|
* The order is the order things are needed in: where the site is on this machine, then how to read its
|
|
* data.
|
|
*
|
|
* ── What used to be here ──
|
|
*
|
|
* An address and a token: where fofos is, over HTTP. That is gone from the screen. The server half is
|
|
* untouched — `/_config` still stores a URL and a token, and the proxy in `api/router.ts` still reads
|
|
* them — but nothing can set them, which is why `useReady` stays hardcoded false and every other
|
|
* section stays locked. The two are the same unfinished change.
|
|
*/
|
|
|
|
export const AdministrationPanel = () => (
|
|
<div className="flex size-full flex-col gap-4 overflow-auto p-5">
|
|
<RootLocationBlock />
|
|
<DatabaseBlock />
|
|
</div>
|
|
);
|