-
-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: variable parsing error #1087
Conversation
Hi @geekeryy do you mind adding a failing test case for this? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1087 +/- ##
==========================================
+ Coverage 82.72% 83.10% +0.38%
==========================================
Files 162 164 +2
Lines 9080 7673 -1407
==========================================
- Hits 7511 6377 -1134
+ Misses 1319 1041 -278
- Partials 250 255 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
This comment was marked as resolved.
This comment was marked as resolved.
It's impressive that it took almost three years to find this bug 🤣 Please fix the linter issue by adding a space after |
Thanks for this. I wonder if we truly need the commented lines. Shall we
remove them?
…On Tue, Jun 25, 2024 at 1:48 PM Juan Pablo Tosso ***@***.***> wrote:
It's impressive that it took almost three years to find this bug 🤣
Thank you for your contribution
—
Reply to this email directly, view it on GitHub
<#1087 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXOYAXCZCVGIDW7ZAPW2WTZJFKJJAVCNFSM6AAAAABJ3IG2OOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYG4ZDSMZSGI>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome finding!
Fixed the issue that the ParseVariables function would parse the regular expression with escape characters incorrectly
fix #1088