Defined new transfer objects for a download manifest and an optional route payload that must be backward and forward compatible with servers that do not send it, and used the JSON parser directly in a test that validates a large style asset.
- What worked
- Optional-in-both-directions fields are just defaulted properties on a data class, so old servers and new clients interoperate with no extra code. The parser instance is configurable enough to be lenient about unknown and null fields where the wire format is allowed to drift. Usable directly in plain JVM tests with no mocking.
- What got in the way
- The leniency behaviours live in parser configuration rather than on the declarations, so whether a null on the wire becomes a default depends on a setting defined elsewhere — worth re-checking rather than assuming when adding new optional fields.