Arbitrary keys bug?#457
Merged
Merged
Conversation
added 2 commits
July 20, 2025 18:29
…ys that contain other keywords (e.g. CONFERENCE_DATE) from getting erroneously replaced.
Member
|
Sorry for very late response. Did you test if this fixes the issue? If so, I'll merge. |
Contributor
Author
|
Yes, it works in the examples I tested (e.g. arbitrary_key then doing ARBITRARY_KEY in the template section). I can add arbitrary keys to the examples, but I thought this might be cleaner |
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.
It seems that this line in templater.py originally would always return None. Since arbitrary keys in the yaml was not working properly, I assume it is meant to return the artbitrary keys. If so, I fixed it, so that it would return arbitrary keys.