-
Notifications
You must be signed in to change notification settings - Fork 22
Improve regex item search: implict word boundaries, chaining and literal matches #1338
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
base: main
Are you sure you want to change the base?
Conversation
datalab
|
Project |
datalab
|
Branch Review |
ml-evs/fix-regex-search-sanitization
|
Run status |
|
Run duration | 08m 00s |
Commit |
|
Committer | Matthew Evans |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
0
|
|
0
|
|
0
|
|
336
|
View all changes introduced in this branch ↗︎ |
925f612
to
40c619a
Compare
1036ffa
to
98301aa
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1338 +/- ##
==========================================
+ Coverage 80.05% 80.07% +0.01%
==========================================
Files 70 70
Lines 4729 4732 +3
==========================================
+ Hits 3786 3789 +3
Misses 943 943
🚀 New features to boost your workflow:
|
- sanitize user input with brackets - match on implicit word boundaries - chain whitespace delimited queries
d604630
to
6681a9e
Compare
93752d6
to
c2c407f
Compare
c2c407f
to
fdb6588
Compare
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.
Seems to work very nicely! The one thing is that I don't understand exactly the rules, i.e. surrounding short vs. long. A slightly longer writeup of the behavior somewhere would be nice so we can reference for future debugging/ additional enhancements.
Closes #1336 by: