Skip to content

Include possible field values in interactive tree #19

Description

@vladvintila

Right now the kubernetes api spec does not include valid field values(enums). But there's an issue to include them, which is quite close:
kubernetes/enhancements#2887

I believe waiting on this issue and then supporting it is what needs to be done, but correct me if I'm wrong.

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