Skip to content

use the new error in the transactionError subscription #201

Description

@bchamagne

Is your feature request related to a problem?

No response

Describe the solution you'd like

We deprecated the reason from the transactionError.
Instead the SDK should use the new propertyerror which is of type :

{
code: Int
data: any
message: String
}

Additional context

I believe this require a major version bump

A util function such as formatError would be great because we might have inception of errors and that would provide great error message (example: "Invalid recipient execution: Condition Failed: still locked")

Epic

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions