envimate/mate-parade

mate-parade's Issues

Use convention instead of boilerplate on leaf types

The minimal amount of code to support a leaf type now is overly verbose.

public class Id {
    public final String value;


    public Id(String value) {
        this.value = value;
    }

    public String getValue() {
        return this.value;
    }
}

If we're encouraging people to use a lot of specific types this should be simpler. I'd like the following to work:

public class Id {
    public String value;
}

Perhaps we can use an annotation for the constructor. But I don't think we need to provide a getValue function. Use the public fields.

mapmate support non-String types

A domain model can contain non-string primitives, such as int or double. These should be supported by the serialization directly, rather than than having to manually convert to/from string.

Deserializing produces a null id in MinimalMapMate example

In the MinimalMapMate Example.deserialize test the user.id is null. It's unclear why, especially as no errors appear to be produced.