-
Notifications
You must be signed in to change notification settings - Fork 8
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
Invisible characters #17
Comments
I'm somehow wary of just ignoring them. Maybe what we could do is after pressing search, the entry in the search bar shows them in a visible form, i.e. their escape code ( |
That sounds great, as long as loogle recognizes the escape code so you can search the replaced version of course. |
Since Loogle uses the lean parser for strings, that should work out of the box. Doing the replacement in Python is a bit trickier. |
OTOH, it probably not worth spending too much thought about this, so if someone opens a PR to the python code that simply strips certain characters form the input right away, I’d probably merge it. |
Having invisible characters in a query (such as "") will cause no results to show up, resulting in identical looking searches with different results.
The text was updated successfully, but these errors were encountered: