Skip to content

Implement sub-set requirement checking #2

@hoijui

Description

@hoijui

As of now, there is only one sub-set defined: the required properties.
It would be useful though, if we have more such sets defined (e.g. recommended and optimal) within OKH or the tooling,
but also to allow external entities to define such sets and publish them in a way compatible with our tooling.

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