-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: add no-regexp-v-flag
(and bump to ES2024)
#31
Conversation
Also: - fix: ensures no-hashbang-comment rule is in TS 2023 - docs: remove unneeded backticks in no-regexp-s-flag rule docs
|
||
let dotAll = `/[\0-\uFFFF]/` | ||
let dotAll = /[\0-\uFFFF]/ | ||
``` | ||
|
||
If you are using it in combination with the `u` flag then you may adjust the pattern: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're coming back to this, it might be good to offer more detail on how workarounds function. This is a little unclear (I know it's not your writing but if you're happy to improve it that would be great!). Can be done here or in a follow up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I'm not so clear on how to improve it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's fine we can follow up on it later.
Co-authored-by: Keith Cirkel <keithamus@users.noreply.github.com>
Co-authored-by: Keith Cirkel <keithamus@users.noreply.github.com>
Good doc suggestions. Applied... |
feat: add
no-regexp-v-flag
(and bump to ES2024)Also:
Realized there was ES2024 and ES2025 too.