Fix #6: Add eager/non-throwing validation for expression syntax errors #136
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
…x errors - Add ExpressionValidator to validate expressions before compilation - Validate regex patterns in IsMatch()/IndexOfMatch() without throwing - Detect unknown function names gracefully - Validate CI modifier usage on functions that support it - Return validation errors via TryCompile() instead of throwing - Add test suite for validation scenarios
- Fix ${regex} to {regex} in log message (was outputting literal text)
- Rename CaseSensitiveFunctions to CaseInsensitiveCapableFunctions
- Add test for IndexOfMatch with invalid regex in Compile()
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.
Fixes #6
Implements eager validation for expression syntax errors, making them non-throwing in the TryCompile path.
Changes
Testing