fix: error when regex is invalid#65
Merged
Merged
Conversation
This file contains hidden or 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
1 participant
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.
This pull request improves the robustness of the
findRuleutility by adding validation for regular expressions and updating its tests to handle invalid regex patterns gracefully. The most important changes are:Robustness improvements
validRegexhelper function insrc/cli/utils/findRule.jsto check if a given regex pattern is valid before using it.findRulefunction to only attempt regex matching if the pattern is a valid regex, preventing runtime errors from invalid patterns.Testing enhancements
src/tests/cli/findRule.spec.jsto ensure thatfindRuledoes not throw an error when encountering an invalid regex pattern in the rules.This closes #63