Parser error reporting limit #672
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
…mit is not yet exposed on the top-level CEL package
jcking
approved these changes
Apr 4, 2023
TristonianJones
added a commit
to TristonianJones/cel-go
that referenced
this pull request
Apr 12, 2023
Introduce a configurable error reporting limit in the parser. This limit is not yet exposed on the top-level CEL package
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.
To ensure that deeply problematic expressions do not overwhelm system resources with large volumes of error reports, introduce a limit of 100 syntax errors by default. This limit may be configured, but the configuration flag is not yet exposed on the top-level
celpackage until it is necessary to do so.