Repository navigation
Validate dashboard YAML before deploy (#60) - #70
Merged
JohanLorenzo merged 1 commit intoOct 9, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A new widget with no
id, or withid: null, used to fail with a generic "Failed to parse dashboard YAML" error. Dashboards now fail before any API call, and the message names the widget and says to writeid: 0. Both inputs stay rejected, so a typo in an existing ID still surfaces as an error.Validation deserializes into the existing dashboard structs, so each error carries the widget path. A second check reports every widget without content in one run.
Evidence,
dashboards deploy reprowith a one-widget dashboard:Before:
After, with no
id:With
id: 0, validation passes and the request reaches the API.Fixes #60