Skip to content

Support bidirectional migrations #8

Open

Description

@adamgundry

At the moment, data can be migrated only from older to newer versions, but in some circumstances we might want the opposite. This would require some thought as the existing changelog format does not include enough information to go backwards (e.g. when a type is removed, we do not record its definition). We need to find the right trade-off between extending the changelog with additional information, supplying appropriate defaults, and warning the user when a backwards migration may lead to invalid data.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    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