fix: properly escape Nix strings everywhere #35
Merged
Conversation
This file contains 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
aksiksi
force-pushed
the
escape-chars
branch
3 times, most recently
from
12e3f65 to
da395f8
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #35 +/- ##
==========================================
+ Coverage 71.70% 71.96% +0.26%
==========================================
Files 6 6
Lines 735 742 +7
==========================================
+ Hits 527 534 +7
Misses 166 166
Partials 42 42 ☔ View full report in Codecov by Sentry. |
aksiksi
force-pushed
the
escape-chars
branch
from
da395f8 to
bb3292d
Compare
aksiksi
changed the title
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.
Fix an issue where special characters were not properly escaped in template, leading to Nix parsing errors.