Handle int64 and uint64 in properties by wrapping it #4253
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.
Summary
We started using structpb.Value to hold the payload of our properties,
but since the Value type is expected to be directly serialized to a JSON
value, all numerical values are treated as float64.
Because we also want to store int64 values, we need to treat them
separately, by storing them as objects instead with the integer value
stringified.
Related: #4171
Change Type
Testing
mostly unit tests
Review Checklist: