Validate function argument contracts - #66
Open
OskarEichler wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Return JMESPath error classes consistently for malformed function calls: validate string
containsneedles, distinguishsumtype/arity errors, require object arguments formerge, and enforce one argument forreverseandto_array.Reproduction
Focused external cases currently leak Ruby
TypeError, classify non-arraysumas arity, or silently ignore extra/missing arguments. The candidate raises the specification'sInvalidTypeErrororInvalidArityError.Verification
Compatibility
Valid calls are unchanged; only invalid argument shapes receive consistent JMESPath errors. Prepared with AI-assisted source review; no repository tests were changed.