Skip to content
This repository was archived by the owner on Apr 23, 2021. It is now read-only.
This repository was archived by the owner on Apr 23, 2021. It is now read-only.

Prevent confusion with empty vs absent model specification #90

Description

@stefanoborini

At the moment, it is my understanding that an empty models: specification means that the CUDS Item is associated to any model. This is a bad idea, because we have to treat the special case of empty as "all" when we do a check for inclusivity (the in operator).

The correct solution is to leave models unspecified if the Item is valid for any model, and consider the empty option logically, as an Item that is not valid for any model.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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