Skip to content

Conflicting changes cause undefined behavior in Transformer during fork synchronization #274

@mindaugasdirg

Description

@mindaugasdirg

In iModel forking scenarios both source and target iModel can be modified and this also means that some changes can be conflicting like updating element in one iModel and deleting it in another. Currently, imodel-transformer ignores all conflicts and tries to iterate iModel like conflicts do not exist, which can cause weird and unexpected behaviors.

I think there is a need to decide how transformer should behave in case of conflicts and add it to the package.

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