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

More information in Error #50

Open

Schuwi opened this issue Jun 13, 2020 · 1 comment

Contributor

Schuwi commented Jun 13, 2020

Knowing where an error in de/serialization happened (byte offset, nbt path) would be very neat.

I haven't looked into how hard this would be to implement yet.

Collaborator

atheriel commented Jun 14, 2020

It’s possible this information is available in the serde-level errors, we may need to propagate it better though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment