Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Notification of deprecated schema properties #26

Open
J0nKn1ght opened this issue Sep 1, 2021 · 0 comments
Open

Notification of deprecated schema properties #26

J0nKn1ght opened this issue Sep 1, 2021 · 0 comments

Comments

@J0nKn1ght
Copy link

There is a closed issue (#13) which indicates that the transaction.processorResponse property has been deprecated. The linked commit actually just corrects the deprecation notice from indicating that statusEvents should be used, to the correct property which is statusHistory.

We're currently using the transaction.processorResponse property returned from a chargePaymentMethod mutation to obtain the transaction legacy code, and so my question really is, when will this mutation stop returning the transaction.processorResponse property from the Sandbox/Live environments, and also how can we be informed of breaking changes that are being made to the GraphQL API in the future?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@J0nKn1ght and others