Skip to content

feat: chart decisions Phase 5 — YAML annotation overrides

Problem

Dataface's chart decision engine automatically selects chart types and visual encodings based on the data shape, but users currently have no way to override or annotate those decisions from YAML. When the engine picks a suboptimal chart type or encoding — for example choosing a grouped bar chart when the analyst wants a stacked one — the only recourse is to manually patch the generated Vega-Lite spec outside the Dataface pipeline. This breaks the declarative YAML workflow and makes dashboards fragile to regeneration. YAML-level annotation overrides would let analysts steer decisions (e.g., force a specific chart type, pin an axis scale) while keeping the decision engine as the default.

Context

Possible Solutions

Plan

  • Finalize override key vocabulary and precedence with existing defaults.
  • Implement parser/decision-engine support for override application.
  • Add audit/debug output so users can inspect why a chart was selected.
  • Create fixtures demonstrating both happy path and conflicting overrides.
  • Update chart-decisions docs with anti-patterns and recommended usage.

Implementation Progress

Review Feedback

  • Review cleared