Add missing parameters to Card and BankAccount services #2102
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.
Why?
There were two issues opened recently in the
V1Cards
andV1BankAccounts
services in the newstripe.Client
:In #2098, we addressed the second issue. This PR addresses the first, where a missing
Metadata
field was reported. The root cause turned out to be that when we generated code forV1Cards
andV1BankAccounts
as part of the newstripe.Client
pattern, there were many missing parameter fields in theCreate
param structs. This PR adds the missing parameters, and handles them appropriately elsewhere in the code.What?
Customer
andAccount
path parameters toBankAccount
andCard
params structs where they were missing.if
/else
in theV1Cards
andV1BankAccounts
services to call the appropriate endpoints.CardCreateParams
andBankAccountCreateParams
.AppendToAsCardSourceOrExternalAccount
andAppendToAsSourceOrExternalAccount
methods.Changelog
V1Cards
andV1BankAccounts
services: ensures the newstripe.Client
pattern supports all parameters previously available inclient.API
for those two services.