Skip to content

chore(deps): update dependency daisyblazor.charts to 0.2.3#17

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/daisyblazor.charts-0.x
Open

chore(deps): update dependency daisyblazor.charts to 0.2.3#17
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/daisyblazor.charts-0.x

Conversation

@renovate

@renovate renovate Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
DaisyBlazor.Charts 0.1.10.2.3 age confidence

Release Notes

phmatray/daisyblazor (DaisyBlazor.Charts)

v0.2.3

Full Changelog: v0.2.2...v0.2.3

v0.2.2

What's Changed

  • fix: complete preset safelist + component a11y/i18n from UI audit by @​phmatray in #​15

New Contributors

Full Changelog: v0.2.1...v0.2.2

v0.2.1

What's Changed

Full Changelog: v0.2.0...v0.2.1

v0.2.0

A genericity release: DaisyBlazor was originally extracted from an app, and a few components still carried that app's hardcoded brand colors and a silent Material Symbols font dependency. This release decouples both. All changes are API/binary-compatible with 0.1.x — the only behavioral change is that some components now follow your active daisyUI theme instead of hardcoded colors.

✨ Theme-aware defaults (no more hardcoded brand colors)

Leaked brand-color defaults now fall back to daisyUI theme tokens. Explicit values are still honored, so this is non-breaking:

  • FeatureHero / FeatureHomePage — gradient falls back to var(--color-primary) / var(--color-secondary) instead of the hardcoded #​1976d2 / #​42a5f5.
  • KpiCard — default accent color is now var(--color-primary) instead of #​4fc3f7.
  • Nav-card hover border falls back to the theme primary.
  • New: BreadcrumbServiceOptions.HomeHref (default "/") — set it for apps mounted under a path base (e.g. /app/).

⚠️ Visual note: if you use FeatureHero, FeatureHomePage, or KpiCard and relied on the old blue/cyan look, pass explicit GradientStart/GradientEnd/Color values to restore it.

✨ Swappable icon font + inline-SVG escape

The Material Symbols web font used to be a silent, forced dependency — inherited transitively by anything rendering an icon (Pagination, Alert, Menu, …). It's now opt-out:

  • New IconOptions — cascade it once near the app root to swap the icon-font class everywhere (it propagates to icons nested inside composites):
    <CascadingValue Value="_icons" IsFixed="true">
        <Router ... />
    </CascadingValue>
    @&#8203;code { readonly IconOptions _icons = new() { FontClass = "material-symbols-rounded" }; }
  • <Icon> now accepts child content — pass inline SVG to bypass the icon font entirely:
    <Icon><svg viewBox="0 0 24 24" class="w-6 h-6">...</svg></Icon>
  • The font requirement and both escape routes are now documented in the styles README.

Material Symbols renders through ligatures, so a FontClass swap is transparent only for a ligature-compatible font that shares Material's names (e.g. another Material Symbols variant). For an arbitrary icon set (Lucide, Heroicons, …), use the inline-SVG escape.

Compatibility

API/binary-compatible with 0.1.x. Zero-config rendering is unchanged except for the theme-aware defaults noted above. 38 component tests green.

v0.1.6

🐛 Bug fixes

Tab strip and Snackbar toast rendered unstyled for component-only consumers

preset.css safelisted component variant classes (tabs-border, toast-end, …) but not the bare base classes (tabs, toast, tooltip, steps, timeline, carousel, chat). daisyUI only emits a component's base rule when the bare class is seen, and these classes are rendered solely inside the compiled components — so apps that use <Tabs> / <SnackbarProvider> without writing the raw daisyUI classes in their own markup got:

  • a tab strip with no layout — the tab headers collapsed into run-together text, and
  • a Snackbar toast that lost position: fixed and fell to the bottom of the page, out of the viewport.

The base classes are now force-generated in all three preset.css copies (Components, the @daisyblazor/tailwind npm preset, and the project template).

<Tabs> active panel was hidden

Tabs selects the active tab in C# and renders the single active panel (.tab-content) as a sibling of the tablist (correct ARIA: a tabpanel beside the tablist). But daisyUI v5 keeps .tab-content at display: none unless it immediately follows the active .tab — an adjacency that never matched this structure, so the panel stayed hidden once the base tabs styles were present. A new scoped Tabs.razor.css forces the already-C#-selected panel visible.

📦 Packages

  • DaisyBlazor.Components 0.1.6
  • DaisyBlazor.Charts 0.1.6
  • DaisyBlazor.Templates 0.1.6
  • npm @daisyblazor/tailwind 0.1.6

Full Changelog: v0.1.5...v0.1.6

v0.1.5

What's Changed

Features
  • FeatureNavCard: restore the gradient "big card" redesign — identity accent bar, eyebrow + heading, circular "go" affordance, and gradient avatar tile. Clickable cards now expose button-role + keyboard (Enter/Space) accessibility. The .nav-card* styling now ships in the package preset (styles/preset.css), and the stale ::deep scoped CSS (which couldn't reach the child-component card root) was removed. Public API unchanged.

Full Changelog: v0.1.4...v0.1.5

v0.1.4

What's Changed

Maintenance release — no DaisyBlazor.Components / DaisyBlazor.Charts source changes since 0.1.3. Rolls up the merged Renovate dependency updates.

Dependencies

Full Changelog: v0.1.3...v0.1.4

v0.1.3

What's Changed

Bug fixes
  • Charts: fix .ToString(_ci) leaking as literal SVG attribute text in LineChart (horizontal gridlines' x2) and DonutChart (guide-circle r / stroke-width). The culture-aware call sat outside the Razor @(...) expression — e.g. @((a - b)).ToString(_ci) instead of @((a - b).ToString(_ci)) — producing invalid attributes such as x2="588.ToString(...)" and SVG console errors. Added a regression test asserting no chart leaks ToString into its rendered markup.

Full Changelog: v0.1.2...v0.1.3

v0.1.2

What's Changed

Features
  • FeatureHomePage: add NavCardsTitle — renders an optional heading above the nav-cards grid, mirroring the existing NavCards slot and the QuickAccessTitle / QuickAccessButtons pairing. Ships with the XML doc comment, the generated API-reference entry, and bUnit coverage (title shown when set, omitted when not).

Full Changelog: v0.1.1...v0.1.2


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants