Skip to content

handle path collisions #18

Description

@bluewingtitan

Right now, modules could target the same path multiple times. Or a subfolder in a folder that is overwritten in another step.

We should detect this and ask for confirmation, since this isn't perfectly defined (or definable) in some edge cases.

We should not deny the user from executing this, as it might still be intended in some way.

We should document clearly, that multiple folder operations onto the same folder will probably lead to unexpected results and should be avoided if possible.

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