refactor: Enable eslint RegEx rules #240
Merged
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
matz3
reviewed
Aug 2, 2024
d3xter666
force-pushed
the
update-eslint-rules
branch
from
55577a8 to
c50991d
Compare
matz3
previously approved these changes
Aug 9, 2024
d3xter666
force-pushed
the
update-eslint-rules
branch
from
c50991d to
0bb33f8
Compare
matz3
approved these changes
Aug 12, 2024
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.
With the introduction of ESLint 9 and the update of
typescript-eslint, there are new rules that will be applied to the code. Those rules are mainly focused on Regex patterns.With #230 those rules have been turned off to keep it consistent with the old behavior.
This change aims to enable those rules.
Note: The base for this change is #230 and not the main branch. This way it's clearer what the real changes are.