feat(ui-dashboard): ChartConfigLike contract + first chart option panels (0.2.1)#302
Merged
Merged
Conversation
… (3b) Foundation for migrating the chart render/option components. Expands the minimal ChartConfigLike (was just yAxis) into a full structural mirror of the proto ChartConfig tree, plus the chart-config enums: - enums: Calculation / Direction / MarkerType / SortBy / ValueFormatter / ValueStyle / PieType / LineStyle - chart.ts: xAxis, lineConfig, valueConfig (+ mappingRules/colorTheme), pieConfig, barGauge, queryValueConfig, tableConfig (+ columnSort), labelConfig, scatterConfig, seriesConfig, dataConfig, timeRangeOverride (timeRange payload opaque), markers All fields optional so a consumer's generated ChartConfig assigns structurally. No proto/private imports. build + tsc clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
First batch of chart option panels into ui-dashboard (phase 3b) — the ones that only need ui-core atoms + the ChartConfigLike contract, no data/sql coupling: - LineControls, LabelControls, PieChartControls, BarGaugeControls proto ChartConfig_* types -> *Like contracts; DisclosurePanel/Checkbox/Button/ NewButtonGroup/HelpIcon from @sentio/ui-core; strict-mode param types. Ladle stories added. build + tsc clean. Deferred to later 3b slices: the value-formatting trio (needs query-value-theme relocation), QueryValueControls (ColorSelect), and the data/sql-coupled panels (Table/Scatter/Yaxis/Xaxis/Data/Series/TimeRangeOverride). Bumps 0.2.0 -> 0.2.1. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
What
Phase 3b foundation + first batch of chart option panels into
@sentio/ui-dashboard.Type contract — expand
ChartConfigLike(was justyAxis) into a full structural mirror of the protoChartConfigtree, plus the chart-config enums:Calculation/Direction/MarkerType/SortBy/ValueFormatter/ValueStyle/PieType/LineStylexAxis,lineConfig,valueConfig(+mappingRules/colorTheme),pieConfig,barGauge,queryValueConfig,tableConfig(+ columnSort),labelConfig,scatterConfig,seriesConfig,dataConfig,timeRangeOverride(timeRange payload opaque),markersOption panels (the ones needing only ui-core atoms + the contract):
LineControls,LabelControls,PieChartControls,BarGaugeControlsDisclosurePanel/Checkbox/Button/NewButtonGroup/HelpIconfrom@sentio/ui-core; protoChartConfig_*→*Like; strict-mode param types. Ladle stories for each.Deferred to later 3b slices
ValueOptions/ValueControls/ValueStringMapping) — needsquery-value-themerelocatedQueryValueControls— needsColorSelectTableControls,ScatterControls,Yaxis/XaxisControls,DataControls,SeriesControls,TimeRangeOverrideVerification
pnpm build(css+js+dts) +tsc --noEmitclean;ladle servelists/compiles all option stories. No proto/private imports. Bumps0.2.0 → 0.2.1.🤖 Generated with Claude Code