-
Notifications
You must be signed in to change notification settings - Fork 277
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
Visual clue for Data Viewer substring search #7628
Comments
Related to #7090 |
What if I just changed it to always include * on the end? That's essentially what it used to do. Instead of exact match it was 'includes' |
That would probably match the wanted behavior for most people. |
@misolori what do you think of the changes here: Essentially what will happen is:
An example.
|
That maps to what I expected 👏 👍 |
Thanks @rchiodo! I like the change. The only question I have is how do we let users know about using "=" for exact match? Maybe a placeholder text "Use "=" for exact match" when they click into the filter box? |
The idea is documentation (see the PR I linked above). We all chatted about it and thought it wouldn't fit. Filter box is usually only 5 to 10 chars wide. |
Here's the text from that pr: Filtering rowsFiltering rows in the data viewer can be done by typing in the textbox at the top of each column. Type a string you want to search for and any row that has that string in the column will be found: If you want to find an exact match, prefix your filter with '=': More complex filtering can be done by typing a regular expression: |
@misolori yep that's what I was thinking but our filter box is too short to fit in the text I guess.. |
We could put a hover tooltip though. Something like:
|
Hover is turning out to be more difficult than I thought. We're using this fluent-ui here and they don't have a convenient way to add a tooltip |
After discussing at standup, we probably need something that makes this work like other search inside of VS code. So an explicit button for
|
Noting that I ran into this in the Golden Scenario this week and I could not figure out how to do an exact match filter. filter-exact-match.mp4 |
I have been looking around for some documentation regarding the use of regex flags with the data viewer but could not find anything. Is this supported and if so what is the proper syntax for using in the data viewer? For say a case insensitive regex search for example which is the /i flag. |
Documentation for the filtering is here: You should be able to enter anything that you can put into a javascript regex but you can't control the global options (like multiline or insensitive). So case insensitivity requires more complex expressions. You basically have to use |
Thank you for the quick response. I looked over the documentation as well as the JavaScript documentation that you sent over. Thank you for sending that. Based on what I read it looks like JavaScript does not support inline mode modifiers such as "(?I)sometext(?-i).*" This is a mode modifier for a case and sensitive search that is inline. I was thinking this could be used as an alternative to global flags. Can you confirm if that is the case? If so are there any feature requests currently for either global modifiers support or inline mode modifier support? If not I will likely put any feature request for it or whatever you would suggest is the best route for requesting this feature. Thank you again for your assistance. |
Javascript doesn't support inline mode modifiers AFAIK. But you can create sets of characters that should match. You can enter a feature request either in the discussions forum: Or by just entering a new issue. |
VS Code 1.61.0-insider + Jupyter extension v2021.9.1001261101
expected: Any value that contains the typed-in string shows up
actual: no value shows up unless an asterisk is added. This is quite confusing. I understand why we added the "*" support but it would be nice to give users visual clues that an asterisk is required if they want to perform substring search
The text was updated successfully, but these errors were encountered: