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.
Fix issue #2269
As suggested by @OTooleMichael, when data type can not be resolved for parameters, using STRING as default type is preferable over INT64 because STRING is the most permissible type and can be casted to any other types.
This PR applies this change from two aspects
to_int64($1)
will expect$1
to have type STRING.[$1]
will have type STRING[].Note
We might still miss default case for some functions. I hope to solve this with fuzzy testing rather than checking each function manually. Meanwhile, since the default input of casting functions has been changed to STRING. User can always use
to_x($1)
to get the expected type from STRING input. I think this is good enough for now.