Skip to content

Conversation

@khanti42
Copy link
Contributor

@khanti42 khanti42 commented Jan 7, 2026

Explanation

What is the current state of things and why does it need to change?

Currently, when wallet_getCallsStatus returns statusCode: 500 (REVERTED), the response only includes the status code without any error context. The transaction controller may have error information available (message, code, RPC details) but it's not being surfaced in the API response, making it difficult for developers to debug why transactions failed.

What is the solution your changes offer and how does it work?

This PR adds an optional error field to the wallet_getCallsStatus response when statusCode: 500. The implementation extracts error information from transaction.error (message, code, name, rpc) when available, and provides a default "Transaction reverted" message when error details aren't present. The error field is only included for REVERTED status, ensuring backward compatibility.

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

@khanti42 khanti42 force-pushed the feat/enrich-wallet-getCallsStatus-error-info branch from 72762ec to 1ab9592 Compare January 7, 2026 09:50
@khanti42 khanti42 force-pushed the feat/enrich-wallet-getCallsStatus-error-info branch from 1ab9592 to cc7eab8 Compare January 7, 2026 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants