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

Consider "toning down" the error UI when unable to deserialise values #1503

Open
JFlath opened this issue Nov 7, 2024 · 0 comments
Open
Labels

Comments

@JFlath
Copy link
Contributor

JFlath commented Nov 7, 2024

At the moment, we report this as Errors were encountered when deserializing this message, which is true, but also doesn't account for the case where the data is actually just raw bytes and so this is expected. We also then show the actual bytes almost as a footer to the list of errors, so it's easy to overlook them.

Perhaps we could emphasise the raw bytes in these cases, and then list that we were unable to match them to any common encoding below?

@weeco weeco added the ui/ux label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants