Skip to content

Migration method seems not to be idempotent #2

@danielo515

Description

@danielo515

Looking at the method that you have for migrating changes, it doesn't seem to be idempotent.
It seems to assume that it is always called from a previous version to a newer version.
Also, it seems that each migrator doesn't get information about the version it is migrated from, unless that is part of the loro_doc itself.

It is expected that each migrator ignores versions that are more up-to-date than what it is designed to migrate?

You only have version one, so it is very hard to try to guess what the workflow will be, so a comment about that would be awesome.

Regards

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions