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.

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

SPIKE: better errors in Freighter client #1633

Open
aristidesstaffieri opened this issue Nov 8, 2024 · 0 comments
Open

SPIKE: better errors in Freighter client #1633

aristidesstaffieri opened this issue Nov 8, 2024 · 0 comments

Comments

@aristidesstaffieri
Copy link
Contributor

We handle displaying errors in a few ways -

  1. Show the raw error and/or stack trace to the user.
  2. Show a generalized error.
  3. Show a user friendly error message mapped to error codes or types.

Can we improve the UX here?
Can we stop showing raw rpc errors and/or stack traces to users?
Should we implement a client only tracing system, where we can provide users trace IDs in their error messages that they can use to communicate their issues. We can then use the IDs to correlate the report to a log.

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

No branches or pull requests

1 participant