Skip to content

Add Permissive Serializer #113

@daym

Description

@daym

Right now, the serializer craps out on the first invalid field value it finds.

This isn't nice for bringup of new generations where we usually have (a few) unknown values on some fields and so the entire serializion will fail--and what do we do then?

Better to have the serializer just warn on fields that have unknown values and then leave it off the json.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions