Skip to content

update-restricted flag is poorly named #339

@gjermundgaraba

Description

@gjermundgaraba

I was unsure what exactly the update-restricted flag meant (side-note: the cli descriptions of the mint-restricted and update-restricted flags are not helpful), so I went into the code to find out.

While mint-restricted sort of makes sense; it restricts how can mint to the creator. I sort of guessed this was what it meant.

But update-restricted was very unclear. It was not clear that it actually mean nobody can update their NFTs. Following the logic of the "mint-restricted" I would perhaps guess the creator could do it.

My suggestion: change the name of that flag to something like "disallow-updating-nfts", or perhaps consider having it the other way around (and false by default): "allow-update-nfts".

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