Add MaybeAccountAddress schema #683
Draft
Conversation
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
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
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.
In some endpoints, the
addressfield was returned as an empty string, while theAccountAddressschema defined it as a required field with theaddressformat.This led to issues with the @ton-api/client generator, which attempted to parse the value as a valid TON address and failed at runtime.
To resolve this, a new format
maybe-addresswas introduced along with a separate schemaMaybeAccountAddress, where theaddressfield has different format for client generator.This allows clients to distinguish between valid addresses and missingvalues without breaking existing behavior for fully populated addresses