Gate a route or nav node on a session, not only a permission #103
Reference in New Issue
Block a user
Delete Branch "session-gate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a third coarse gate to the plugin contract:
session: truetakes any signed-in user, with nogrant to hold.
src/auth/gate.tsis the one home of the rule the plugin router, the host's ownroute table, the menu and discovery all read.
Every route and nav node now names exactly one gate, spelled
true: discovery refuses adeclaration that names none, names two, or spells a flag anything but
true, so a forgotten gatefails the boot instead of publishing a page.
HOST_API_VERSIONgoes to 0.4.0. A host built before this readssessionas no gate at all andwould serve the page to anonymous visitors, so the minor is what makes it refuse the plugin instead.
The reference plugin gains
/scheduling/mine, scoped at the upstream by the visitor's identity idrather than their email, and re-filtered in the handler so a backend that ignores the scope cannot
leak through the page.