Skip to content
This repository was archived by the owner on Jan 27, 2024. It is now read-only.
This repository was archived by the owner on Jan 27, 2024. It is now read-only.

Examine common migration patterns #3

@seagreen

Description

@seagreen

Users will often want to expand Plate schemas while still keeping backwards compatibility with old data. Lets examine some of the ways this can play out.

Adding a new field to a sum type

100% backward compatibility with old data. Nice.

Adding a new field to a product type

Currently this always breaks backwards compatibility. We could avoid some of this in two ways: either by allowing optional fields to be missing or by allowing defaults to be set. This ties in to issue #2.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions