flake.nix: Fix ambiguous backslash-escape in the version number regex - #225
Merged
Conversation
The latest version of lix (v2.95.1) has deprecated \. as a string escape as it is ill-defined, issuing this warning now: warning: \. is an ill-defined escape. You can drop the \ and simply write . instead. Use --extra-deprecated-features broken-string-escape to silence this warning. But unfortunately, using "." doesn't carry the intended meaning. What we need to do here is to use "\\." to match a regex-escaped period. Signed-off-by: Andreas Fuchs <asf@boinkor.net>
antifuchs
force-pushed
the
push-zzxnrrprpuqz
branch
from
April 4, 2026 14:49
9002810 to
fb9393e
Compare
mikeodr
approved these changes
Apr 7, 2026
Contributor
|
Thanks for the PR! |
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.
The latest version of lix (v2.95.1) has deprecated . as a string escape as it is ill-defined, issuing this warning now:
But unfortunately, using "." doesn't carry the intended meaning. What we need to do here is to use "\." to match a regex-escaped period.
This PR fixes the ambiguity, ensuring the regex matches the intended target string unambiguously.