Skip to content

Notification of deprecated schema properties #26

@J0nKn1ght

Description

@J0nKn1ght

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions