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

Open
anton-trunov opened this issue Nov 8, 2024 · 0 comments · May be fixed by #1111
Open

Improve error reporting for bounced messages with missing fields #1021

anton-trunov opened this issue Nov 8, 2024 · 0 comments · May be fixed by #1111
Labels
errors Error reporting mechanism ux
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.
@anton-trunov anton-trunov added errors Error reporting mechanism ux labels Nov 8, 2024
@anton-trunov anton-trunov added this to the v1.6.0 milestone Nov 8, 2024
@i582 i582 linked a pull request Dec 3, 2024 that will close this issue
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
errors Error reporting mechanism ux
Projects
None yet
Milestone
v1.6.0
1 participant
@anton-trunov