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

Improve error reporting for bounced messages with missing fields #1021

Closed
anton-trunov opened this issue Nov 8, 2024 · 0 comments · Fixed by #1111
Closed

Improve error reporting for bounced messages with missing fields #1021

anton-trunov opened this issue Nov 8, 2024 · 0 comments · Fixed by #1111
Labels
scope: errors Error reporting mechanism (src/error)
Milestone
v1.6.0

Comments

@anton-trunov
Copy link
Member

A typical error message for a large bounced message looks like this:

Type bounced<"Withdraw"> does not have a field named "amount"

The error message should include the info why some field is missing. This should prevent issues like #1020, #940, #54.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
scope: errors Error reporting mechanism (src/error)
Projects
None yet
Milestone
v1.6.0
1 participant
@anton-trunov