Skip to content

add serialization/deserialization infrastructure for v3.2 #20

@baywet

Description

@baywet

following #2, #19, the serialization and deserialization tests for 3.1 need to be duplicated for 3.2 so we can later adapt them to the new fields, and ensure that there are no regressions.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions