pastilhasandClaude Opus 5
dcbc9b102c
one sidecar, one permission, one install — and two screens, because Calendar and Contacts are two places you go rather than two sections of one page. the first plugin to declare `screens`, which the platform gained for this. what moved: the radicale sidecar, the four routers, the panel apps, the app-password table and the settings form. the form became a modal on the calendar screen — a plugin ships panels and cannot contribute a settings section, which is the same wall the email plugin hit and the same answer. the routes are /calendar and /contacts, not /caldav/calendar. they were core routes and keeping them is not cosmetic: a bookmark, a dock tile someone arranged, and a persisted layout all address them. only a first-party plugin may choose its own segment; a third-party one is confined to /p/<publisher>/. four paths outside /api come with it, above the account gate, because phones are not browsers: DAVx5, iOS and thunderbird send HTTP basic on every request and have nowhere to put a JWT. that is not "open" — the sync door demands a scoped app password and resolves it to one user before radicale sees anything. two things deliberately unchanged. the table is still dav_app_passwords, not caldav_app_passwords: installs hold real rows and a naming convention is not worth a data migration on a live machine. and the panel names still resolve through the platform's catalogs, so the six locales they had as core screens survive rather than dropping to english to make the refactor tidier. per-user was already true and is worth writing down because the config said otherwise: the sync door resolves an app password to an account, tells radicale that id is the principal, and owner_only does the rest. the comment claiming "the owner is the only principal that exists" had been stale since multi-user landed on 2026-08-07. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043
31 lines
1.3 KiB
TypeScript
31 lines
1.3 KiB
TypeScript
import { useGlobal } from 'hooks/useGlobal';
|
|
import { Dialog, DialogContent, DialogHeader, DialogTitle } from '@/components/ui/dialog';
|
|
import { AppPasswords } from './AppPasswords';
|
|
|
|
/*
|
|
Sync setup, as a modal rather than a settings page or a panel.
|
|
|
|
It was a section in the platform's Settings → Integrations, which a plugin cannot contribute to: a plugin
|
|
contributes panels and nothing else. A panel was the obvious replacement and does not work either —
|
|
`PluginScreen` renders the workspace `locked`, so a panel outside the default layout is unreachable and
|
|
one inside it would spend a fifth of the screen on a form you touch twice a year.
|
|
|
|
So it follows the email plugin, which had already solved exactly this: a global holds "is it open", any
|
|
panel can set it, and the panel that mounts the modal renders it once.
|
|
*/
|
|
export const useAppPasswordsModal = () => useGlobal<boolean>('CALDAV_APP_PASSWORDS_OPEN', false);
|
|
|
|
export const AppPasswordsModal = () => {
|
|
const [open, setOpen] = useAppPasswordsModal();
|
|
return (
|
|
<Dialog open={open} onOpenChange={setOpen}>
|
|
<DialogContent className="max-h-[85vh] max-w-3xl overflow-y-auto">
|
|
<DialogHeader>
|
|
<DialogTitle>Sync to your phone</DialogTitle>
|
|
</DialogHeader>
|
|
<AppPasswords />
|
|
</DialogContent>
|
|
</Dialog>
|
|
);
|
|
};
|