Add missing billing and shipping entities to payment resource - #11
Merged
Conversation
Contributor
|
Thank's, could you just update the Readme to replace Customer by Shipping and Billing Plz. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This was missing from the previous update that added support for the latest version of our API.
With this PR, the
Paymentresource can handle both old-schoolCustomer, orBillingandShipping, depending on the answer from the API. It is however up to the user to know which one of those they need to use, depending on the version of the API they specified. It would be nice someday to fully type the interface into our python classes.