Updating IssuingCardDetails.Number json tag to 'number' #697
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
…atch the response from the API
|
@JessicaCGlenn Thanks a lot for fixing my mistake, sorry about the trouble! Going to release this now :) |
|
@JessicaCGlenn I just released it as 49.2.0, thanks again for the work! |
|
You're very welcome, thank you for the speedy response!! Have an awesome week :-) |
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.
Currently the IssuingCardDetails struct returns with a zero value for Number, this is because the json tag in the type declaration is set to 'type' and the API request is returning 'number'.
This pull request simply changes the json tag in the IssuingCardDetails declaration to 'number' to fix this issue.