coerce nil numbers to 0 in jmespath codegen #565
Merged
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.
There's an undocumented quirk in jmespath (as far as i could find) where
nil
numerics are coerced to 0 for order comparison.e.g.
This fixes that in codegen. We caught this while attempting to turn on generated jmespath waiters for
autoscaling
in the Go SDK. This will be further verified when those changes are pulled in there.