-
Notifications
You must be signed in to change notification settings - Fork 47
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
Remove 'wildcard' search option #549
Comments
@flodolo @TheoChevalier @SkySymbol pinging active people :) |
btw, I would also rename "Whole word" as "Contiguous words", we use the regex wording for the feature and I think nobody gets what it actually means |
Absolutely 'yes' for wildcard, I'm not convinced about 'Whole word': I use it exactly to search for the entire word, e.g. cookie (i.e. I don't want 'cookies'). 'Contiguous words" sounds like a search for "open window" should only return a search with strings that contain "open window", in that order. |
Agreed for wildcard, never used it nor understood it. |
ok, so let's scrap wildcard and brainstorm on the right wording for "whole word" as we have several use cases, like the one by flod with a single word and the one I have when I want to return strings that have contiguous words seen as a single string, ex: I like the tooltip ideas that we could add to all options actually, I would put that in a separate issues as a good first bug. |
+1 for the wildcard search option, but I disagree for renaming the whole word feature, as it seems to be the correct appellation. See for example this post on Stackoverflow. |
the problem with the naming is that the people that use Transvision don't know what a regex is, so the question is not what the right naming is technically, but what the right naming is to make the feature understandable by end-users. |
I removed the wildcard option in the branch I am working on for Issues #320 |
Issue #549 remove wildcard search option
The reasons are:
Thoughts?
The text was updated successfully, but these errors were encountered: