-
-
Notifications
You must be signed in to change notification settings - Fork 784
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
over 32 characters #38
Comments
For clarification, are you referring to the |
That is correct. str.match(new RegExp(searchStr, "ig") might also be a solution, but it would be a lot slower. |
Ok, I will put in some thoughts on this. Meanwhile, let's make this a feature request. Thanks! |
+1, not sure if this project is still alive, but if yes, this would be sweet |
Is there a reason for not switching algorithms at 33 characters to an exact match algorithm? It would be seemless to the user and improve user experience (most people typing that much are wanting a fairly exact match anyway).
As it stands in my current project, I have to deal with the error by checking the length and falling back to str.indexOf(searchStr) each time. Building this in seems much more desirable.
The text was updated successfully, but these errors were encountered: