chore(jq): Report an error when the compilation fail #274
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
lquerel
commented
Jul 31, 2024
| @@ -43,10 +43,22 @@ impl Filter { | |||
| filter: filter_expr.to_owned(), | |||
| error: "No parsed expression".to_owned(), | |||
| })?; | |||
| let filter = ctx.compile(parsed_expr); | |||
| if !ctx.errs.is_empty() { | |||
There was a problem hiding this comment.
Strangely, ParseCtx.compile(...) doesn't return a Result and forces us to check the errs field, as was done in the past... I opened an issue in the jaq project to improve that in the future.
lmolkova
approved these changes
Jul 31, 2024
jsuereth
approved these changes
Jul 31, 2024
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.
The interface of the method
ParseCtx.compilein JAQ is error prone and it's a bit too easy to forget to check the errors. This PR fix this issue.Closes #264