Skip to content

config.md format: should capability fields be nested directly under capabilities? #83

@caozhuozi

Description

@caozhuozi

There is another capabilities field described at the top level of the config spec. After investigating the image-spec, this seems to be not a convention. To ensure alignment and avoid confusing, should the capabilities fields be restructured to nest directly under the capabilities field?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions