Repository navigation
Validate each message against the schema its own keys resolve to - #127
Merged
isudana merged 1 commit intoNov 12, 2026
Merged
Conversation
Schemas are now held per resolved key list, bounded with least-recently-used eviction, and the one a message uses is read under the existing lock.
isudana
approved these changes
Nov 12, 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.
A dynamic schema key is now matched against a cache keyed by each message's own resolved keys, instead of a single schema shared by every message. The cache is bounded with least-recently-used eviction so it cannot grow without limit.