Skip to content

Use explicit defaults in fluent chart builders - #3170

Merged
tabuna merged 1 commit into
masterfrom
fix/chart-fluent-defaults
Oct 22, 2026
Merged

tabuna merged 1 commit into
masterfrom
fix/chart-fluent-defaults

Conversation

@tabuna

@tabuna tabuna commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Build each chart type through a native fluent chain with explicit Stimulus defaults. Line, bar, mixed, pie and percentage settings now live alongside their builder instead of a shared list of presence checks.

Keep presence checks only for responsive width, native palette fallback and visibility choices affected by automatic legends or frameless mode. Preserve every PHP-supported option: Chart::options() exposes the full allowlist, and Blade transports gradient endpoints. Gradients use explicit opacity defaults when enabled. Endpoint-only hand-written HTML no longer implicitly enables a gradient; PHP always emits its enabled flag.

Validation: 19 real Stimulus tests and 17 PHP chart tests (47 assertions) pass. Chromium compared old and new SVG output across 28 scenarios covering all five types, frameless overrides, gradients and dataset overrides; output matched after normalizing generated identifiers. Production build, formatting and manifest hash/SRI checks pass. PHP/Blade and unrelated local changes are untouched.

CI on d648d9f: all 24 PHP/Laravel matrix jobs, chart-controller tests, code style, coverage, Composer and spelling passed. Psalm and Semgrep match the stored master diagnostics. Dusk remains failing after one isolated rerun: notification badge timeout, SideMenuTest height assertion, and ItemAddChildScreenFlowTest modal text assertion. The initial attempt also had a logout timeout that did not recur. These failures are disclosed; the full CI suite is not green. No unrelated test fixes are included.

@tabuna
tabuna merged commit bad3af7 into master Oct 22, 2026
55 of 60 checks passed
@tabuna
tabuna deleted the fix/chart-fluent-defaults branch October 22, 2026 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant