If a variable name is passed to the get_metadata templatetag, it shou… #7
Conversation
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
…ld pop the value into the top-most context dict instead of the bottom-most context dict.
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.
…ld pop the value into the top-most context dict instead of the bottom-most context dict.
This is a bug with the current implementation. Let's say I have the following in my template code:
it will add
metainto the bottom-most context dict, so if there's another context dict on top with a variablemeta, it will override the value here and my meta information won't be displayed (or even worse, it'll display wrong/gibberish information).You can avoid this scenario by choosing a unique variable name here, but I think this bug should be fixed at the source.