Fixing long integers when printing in scientific notation#32
Merged
Fixing long integers when printing in scientific notation#32
Conversation
akiradev
approved these changes
Jul 23, 2025
Contributor
akiradev
left a comment
There was a problem hiding this comment.
Changes look sound. Thanks for updating the model from the api specification.
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
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.
Long integers were previously stored as the
Numbertype, which caused some properties of theDecisionobject to be printed in scientific notation. This PR regenerates the code using the latestapi-specification, where object schemas and data types are correctly defined, generating proper type handling and expected output formatting.The PR also includes other necessary updates based on recent changes to the
api-specification.