fix(api)!: endpoint expects amount of new allocation price to be a string, not a number #226
Conversation
This file contains 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
![stainless-app[bot]](https://avatars.githubusercontent.com/in/378072?s=60&v=4){kind=small}
…ring, not a number # Migration This change is fixing the SDK to use the correct `string` type expected by the API. The spec was incorrectly specifying a type `number` but the endpoint expected a string. While this change is technically an SDK breaking change the previous types weren't accurately representing the API behaviour. To migrate, be sure to use a string representation of the new allocation price amount.
stainless-app bot
added a commit
that referenced
this pull request
Jun 25, 2024
…ring, not a number (#226) # Migration This change is fixing the SDK to use the correct `string` type expected by the API. The spec was incorrectly specifying a type `number` but the endpoint expected a string. While this change is technically an SDK breaking change the previous types weren't accurately representing the API behaviour. To migrate, be sure to use a string representation of the new allocation price amount.
Merged
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.
Migration
This change is fixing the SDK to use the correct
stringtype expected by the API. The spec was incorrectly specifying a typenumberbut the endpoint expected a string.While this change is technically an SDK breaking change the previous types weren't accurately representing the API behaviour.
To migrate, be sure to use a string representation of the new allocation price amount.