[ExpressionLanguage] Add more configurability to the parsing/linting methods #53806
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.
When linting/parsing an expression, two kinds of errors can be thrown: a syntax error (for which the parser cannot recover) or an unknown variable/function error (which does not block the parser).
When linting an expression, currently you can ignore unknown variables by passing
null
instead of the valid variable names tolint()
orparse()
, but you cannot ignore unknown functions. For some use cases, it might be needed to just validate the syntax.This PR allows developers to ignore functions and/or variables the "proper way" with flags as a new argument to these methods:
Passing
null
to the$names
argument is deprecated:Before:
After: