Repository navigation
Conversation
Custom contexts are tagged through autoconfiguration, which gives them priority 0. That is higher than both built-in contexts, so a context that always returns a value silently disables the toggler: the button still writes the cookie, but CookieBasedVatContext never gets asked. Document the ordering, list the built-in priorities, and show how to tag a context explicitly to sit below the customer's own choice. Also fixes 'with our without VAT' in the same paragraph. Claude-Session: https://claude.ai/code/session_01P9NzuVPQGvaVR97HZFq98a
This was referenced Aug 23, 2026
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
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 README tells you to implement
VatContextInterface, but not the part that decides whether your context actually works.Custom contexts are tagged through
registerForAutoconfiguration(), which gives them priority 0. Both built-in contexts sit below that (CookieBasedVatContextat -90,DefaultVatContextat -100), so a custom context that always returns a value silently disables the toggler — the button still writes the cookie, and nothing ever reads it. That is a confusing thing to debug from the symptom ("the toggle button does nothing"), and nothing in the docs points at it.This documents the ordering and the fall-through contract (throw
NoVatContextExceptionto defer), lists the built-in priorities in a table, and shows how to tag a context explicitly so it is consulted after the customer's own choice.Also fixes "with our without VAT" in the same paragraph.
No code changes.
Addresses the second architecture item in #5.
https://claude.ai/code/session_01P9NzuVPQGvaVR97HZFq98a