Skip to content

Schema V2: Revisit strategy for optional properties and applying defaults #103969

@axelavargas

Description

@axelavargas

Taken from: #https://raintank-corp.slack.com/archives/C07QVGH37D4/p1744211611230779

Context

When implementing dashboards v2 endpoint, there were a lot of required parameters in the CUE schema. This opened the conversation of intentionality of these required parameters:

Should we required fewer parameters to create a minimal dashboard? (title and nothing more)

We also saw the same ask for these use cases:

  • In dynamic dashboards: Make columnWidthMode and rowHeightMode optional (default to standard )
  • Could we remove default values from saved schemas for template variables? they have their default values when dashboard is created

The vision of the new schema

Users found schema v1's JSON model verbose and filled with defaults. We aim for smaller JSON with the new schema.

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions