-
Notifications
You must be signed in to change notification settings - Fork 578
🐛 trip surrounding quotes that may have been added by extractCommand #4736
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
Conversation
Signed-off-by: fixedpoint <961750412@qq.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4736 +/- ##
==========================================
+ Coverage 66.80% 67.87% +1.06%
==========================================
Files 230 249 +19
Lines 16602 19075 +2473
==========================================
+ Hits 11091 12947 +1856
- Misses 4808 5268 +460
- Partials 703 860 +157 🚀 New features to boost your workflow:
|
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.
Change looks reasonable for the linked issue, I just need to check something out my comment week when I have more time.
|
This pull request has been marked stale because it has been open for 10 days with no activity |
|
Back from vacation, going through my backlog from before and reopenning stale PRs |
What kind of change does this PR introduce?
bug fix
(Is it a bug fix, feature, docs update, something else?)
What is the current behavior?
What is the new behavior (if this is a feature change)?**
URLs surrounded by single quotes ('https://example.com') are properly detected
URLs surrounded by double quotes ("https://example.com") are properly detected
URLs without quotes continue to work as before
Proper pinning validation now works for all quote styles
Tests for the changes have been added (for bug fixes/features)
Which issue(s) this PR fixes
Fixes #4733
Special notes for your reviewer
Does this PR introduce a user-facing change?
No.
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)