feat(no-global-regexp-flag-in-query): enable by default #660
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Belco90
approved these changes
Oct 2, 2022
|
Can you resolve the conflicts? I'll merge it after that. |
BREAKING CHANGE: enable no-global-regexp-flag-in-query for all libraries by default
|
🎉 This PR is included in version 6.0.0-alpha.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
MichaelDeBoey
added
v6
MichaelDeBoey
pushed a commit
that referenced
this pull request
Oct 4, 2022
…660) BREAKING CHANGE: `no-global-regexp-flag-in-query` is now enabled by default in all configs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: enable no-global-regexp-flag-in-query for all shared configs by default
Checks
npm run generate:rules-list)npm run generate:configs)Changes
no-global-regexp-flag-in-queryby default for all shared configsContext
Resolves #618