Fix: track shadowed jinja variable assignments correctly#5503
Merged
Conversation
izeigerman
approved these changes
Oct 8, 2025
treysp
force-pushed
the
trey/jinja-var-shadowing
branch
2 times, most recently
from
3254eb3 to
6902806
Compare
treysp
force-pushed
the
trey/jinja-var-shadowing
branch
from
6902806 to
f2df3b8
Compare
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
2 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.
If a var name is used on both the right- and left-hand sides of a jinja assignment, we don't currently track the right side correctly.
Example:
{% set model = model.path %}should trackmodel.path.