Document deprecated dashboard fields in the create-dashboard skill#39
Merged
Conversation
The bundled skill still taught two authoring forms that the schema unification removed: bare chart `x`/`y` column names and `file:` query references. Fix the chart example to use axis encoding objects and inline queries. Add a "Deprecated Fields" section that maps every removed field to its current replacement (chart x/y objects, inline/named queries, metric value encoding, separate-file semantic models) and instructs the agent to refactor any of them it encounters in an existing dashboard.
mustafa3rsan
approved these changes
Jun 22, 2026
DjamilaBaroudi
approved these changes
Jun 22, 2026
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.
Summary
The bundled
create-dashboardskill had drifted behind the schema-unification breaking changes. It still taught two authoring forms that no longer validate:x: region/y: [revenue](bare column names) —x/ynow require axis encoding objects ({ field: ... }).file: queries/revenue.sqlquery references — removed; queries are inlinesql:or a namedquery:(TSXinclude()still works).This PR:
x: { field: region }/y: { field: [revenue] }and corrects the query-reference guidance.Deprecated → replacement
x: col/y: [col]x: { field: col }/y: { field: [col] }file: path.sqlsql:or namedquery:(TSXinclude())column/prefix/suffix/formatvalue: { field, type, format }semantic:blocksemantic/*.yml+model:Grounded in the actual schema/loaders, not assumptions — confirmed
include()is still supported (pkg/dashboard/jsloader.go), so it is not listed as deprecated.Testing
make testdac validate(passes)docs/already teaches the correct forms (no stale docs)Checklist
docs/— already current; no changes needed