update type of addressFormat to string | undefined #243
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
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.
Pull Request Description
The bug fix involves correcting the data type for the addressFormat property in the SDK code. Currently, the addressFormat is defined as a number in the code. The correction should update the data type to a string | undefined for the addressFormat property in the AddressResponse interface. This adjustment ensures consistency and compatibility with the actual data type used for addressFormat in the underlying implementation.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Ran build command and used the new custom SDK in my Express app. Works fine now and I do not see the compile-time error. I am using Typescript in the Express app.
Checklist: