Skip to content

Nested types should have schema fields, in particular defaultValue #70

Description

@thomasjm

Currently, schema items of type "list" have a listType that is basically just { type: "string"; }. It lacks the required fields of a normal schema item, like "title" and "defaultValue." The lack of defaultValue means that UIs need to come up with their own default value based on the type, which is not ideal.

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