-
Notifications
You must be signed in to change notification settings - Fork 91
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
RegExp slash escapes not parsed correctly #68
Comments
Yeah, the regexp parsing leaves a bit to be desired: Line 83 in 1853a6f
We should enhance it to at least take into account escape sequences and character classes. |
My situation was easy to work around, so this is not something that's blocking me. I can have a look at it later, if you are interested in a PR to fix the problem. |
Sure, send one over. |
As a workaround you can use the unicode code for
|
@toefraz I "optimized" your code. 🤣 |
Will this ever be fixed? |
Using the following snippet in the ESQuery demo:
None of these queries is parsed correctly and all fail with an error:
[value=/foo\/bar/]
[value=/foo\\/bar/]
[value=/foo\\\\/bar/]
I'm using
tsquery
to write an import-location-specific TSLint rule for RxJS and the RegExp issue appears to be an upstream problem with this package.The text was updated successfully, but these errors were encountered: