fix: don't leak variables from not blocks into the outer scope - #209
Merged
Conversation
Variables created while generating a `not` subschema stayed in the generator's variable-tracking set, so outer keywords like `additionalProperties` reused them instead of emitting their own assignments. Since the `not` block only succeeds by raising partway through, validating a passing document raised UnboundLocalError. Fixes horejsek#208 Assisted-by: ClaudeCode:claude-fable-5
This was referenced Jul 21, 2026
|
@horejsek Would you mind sharing whether this is likely to be merged in the near future? Thank you for your time and consideration. |
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
3 participants
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.
This is a proposed fix for top level not generating invalid Python code. Turned out to be a one-line fix.
Fixes #208
🤖
Assisted-by: ClaudeCode:claude-fable-5