refactor: fix error on multiline string and use uv #29
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
JuroOravec
commented
Jan 25, 2026
| "template_string(context, source, {}, filters, tags, {})", | ||
| token_tuple, value.value.content | ||
| )), | ||
| ValueKind::Variable => { |
Contributor
Author
There was a problem hiding this comment.
Here we wrap those values in triple quotes ot safely handle newlines.
I ahve already implemneted this in Citry before, but turns out I forgot to add it here.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Part of django-components/django-components#1255.
The legacy tag parser wasn't handling newlines inside strings properly. I fixed it by wrapping the content in triple quotes
"""and escaping"->\". So that the entire string can be kept as is, but still handle newlines.While at it I also:
uvinstead ofrequirements.txt