Increase number-like data types' precision #36
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.
To avoid breaking changes in the SDK in changes to precision in the OAS that are allowed (eg, reducing precision in fields only used in responses)
The different number types in OAS are described here. The aim is to have all
"type": "number
generated asfloat64
and all"type": "integer"
fields generated as int64.To check that this is working, you can add one of each possible number-like data-type to an OAS structure and generate the SDK: