MergeYaml recipe: Handle ParseError LSTs #5097
Open
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.
What's changed?
validate
function can now handle wrong input yaml (it fails gracefully, as it is supposed to be)incoming
field is parsed once it is needed in the MergeYaml recipe.What's your motivation?
The MergeYaml recipe throws a ClassCastException if invalid Yaml is provided (for instance a ParseError LST). Normally the YamlIsoVisitor does only run for yaml sources:
But the MergeYaml recipe does already do some parsing work for the
incoming
field, which is executed by the JVM before theisAcceptable
has been called. This PR changes this behaviour to start parsing it once it is used.In addition, this change improves performance for all use of the MergeYaml recipe with a
$
key. In that case, theincoming
field is not used at all, allowing an unnecessary parse step to be skipped.