Skip to content

Default value in form format #669

Open
@nicklasb

Description

@nicklasb

I know that it is possible to have default values in the JSON Schema, however, that is not always sufficient:

  1. When you "inherit" parts of schemas($ref) into another, you sometimes want to add or change defaults, especially when there are multiple choices.
  2. In the UI, there are certainly cases where the defaults are more dynamic.

I am thinking that perhaps this pushes it beyond "good to have" and into "commonly usable".

Or should this be better handled in some other way? Defaults is a little tricky when it comes to where they belong.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions