Update to regexp-ast-analysis@0.2.2
#228
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
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.
While working on #214, I noticed that I could drastically simplify the code if only
getFirstCharAfterwas able to properly handle word boundary assertions. So I added that.regexp-ast-analysis now supports word boundary assertions properly in all
getFirst*Char*functions.This will help me implement #214 but it also immediately improves our existing rules that use the
getFirst*Char*functions. Right now, these areno-useless-assertions,no-useless-lazy,prefer-character-class, andprefer-predefined-assertion.regexp-ast-analysis@0.2.1 added support for the
dflag, so this update also works towards #217.