SchemaValidator per-resolver cache clarification#1191
Merged
p1c2u merged 1 commit intoMay 29, 2026
Conversation
p1c2u
force-pushed
the
feature/schema-validator-per-resolver-clarification
branch
from
404b1c7 to
72abf0e
Compare
p1c2u
changed the title
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.
jsonschema-path0.5 (which pullspathable0.6.0) changed the identity model:SchemaPathis now anAccessorPath, and its identity key is (parts, accessor) — not parts alone.SchemaAccessor.__eq__/__hash__discriminate byid(self._node)andid(self._path_resolver), i.e. per-spec/per-resolver reference identity.So the cache key is already effectively per-resolver.
Even two specs with identical content don't collide, because the accessor is keyed on object identity (is), not content.