Skip to content

Require a non-empty name for Blueprints #5010

@tucked

Description

@tucked

Things do not work correctly if a Blueprint is given an empty name (e.g. #4944).
It would be helpful if a ValueError was raised when trying to do that.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions