Skip to content

Improving serialization error messages #298

Open
@Machine-Maker

Description

@Machine-Maker

In a bunch of places, I think exceptions should include 3 things. The input value (string for deserialization, object for serialization), the type (expected type for deserialization, initial type for deserialization), and the exact NodePath to that point.

And this should be consistent everywhere. For example the BooleanSerializer has 2 of those, but doesn't give the exact input value, just that it couldn't convert a String into a boolean.

I think there are some special cases like Maps where some more indepth stuff should be done. For example the message should say if it was a key for value that failed. I did some of this stuff for Paper making my own MapSerializer (see here)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions