A link can set which kinds the timeline shows - #166
Merged
Conversation
The kind filter was state a visitor set in the menu and nothing else could reach: a page that wanted to send someone to the roles alone, or to the community work alone, could only send them to the whole ledger. ?kinds= names the kinds to show, by name and in any case, comma-separated; those are on and the rest off. The page reads it the way it reads ?lang=: once, on arrival, then strips it from the address and remembers the selection as if the menu had been used. So the link hands the visitor a view, nothing they copy afterwards carries it, and the rule that the selection is state and not a place still holds — the address is read, never written. A name the model does not know is dropped, a list naming no kind at all is ignored whole rather than emptying the ledger, and a hash on the same link still lands: the linked row's kind is turned on if the list left it off. The ledger check asserts all of it, and that the address comes out clean. Verified: npm run verify passes; og:check after npm run og, pages:check, design:check, test:og, test:dupes, conventions-check and conventions-sync check pass; the timeline card re-rendered to the same pixels, only its stamp changed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The kind filter was state a visitor set in the menu and nothing else could reach: a page that wanted to send someone to the roles alone, or to the community work alone, could only send them to the whole ledger.
?kinds=names the kinds to show, by name and in any case, comma-separated; those are on and the rest off.The page reads it the way it reads
?lang=: once, on arrival, then strips it from the address and remembers the selection as if the menu had been used. So the link hands the visitor a view, nothing they copy afterwards carries it, and the rule that the selection is state and not a place still holds — the address is read, never written. A name the model does not know is dropped, a list naming no kind at all is ignored whole rather than emptying the ledger, and a hash on the same link still lands: the linked row's kind is turned on if the list left it off. The ledger check asserts all of it, and that the address comes out clean.Verified: npm run verify passes; og:check after npm run og, pages:check, design:check, test:og, test:dupes, conventions-check and conventions-sync check pass; the timeline card re-rendered to the same pixels, only its stamp changed.
🤖 Generated with Claude Code