Skip to content

Issue with unique name of level #104

Description

@benjaminbours

When forking an existing level, the current behavior is prefixing _forked to the name, that reach very quickly an error if you fork 2 times the same root level, because it will tell you the name already exist.

Create a naming convention that is more scalable than this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    APIMostly related to the HTTP APIClientMostly related to client codeinvalidThis doesn't seem right

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions