chore(deps): update dependency daisyblazor.charts to 0.2.3#17
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency daisyblazor.charts to 0.2.3#17renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
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.
This PR contains the following updates:
0.1.1→0.2.3Release Notes
phmatray/daisyblazor (DaisyBlazor.Charts)
v0.2.3Full Changelog: v0.2.2...v0.2.3
v0.2.2What's Changed
New Contributors
Full Changelog: v0.2.1...v0.2.2
v0.2.1What's Changed
Full Changelog: v0.2.0...v0.2.1
v0.2.0A 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 tovar(--color-primary)/var(--color-secondary)instead of the hardcoded#​1976d2/#​42a5f5.KpiCard— default accent color is nowvar(--color-primary)instead of#​4fc3f7.BreadcrumbServiceOptions.HomeHref(default"/") — set it for apps mounted under a path base (e.g./app/).✨ 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:IconOptions— cascade it once near the app root to swap the icon-font class everywhere (it propagates to icons nested inside composites):<Icon>now accepts child content — pass inline SVG to bypass the icon font entirely: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.csssafelisted 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:position: fixedand fell to the bottom of the page, out of the viewport.The base classes are now force-generated in all three
preset.csscopies (Components, the@daisyblazor/tailwindnpm preset, and the project template).<Tabs>active panel was hiddenTabsselects the active tab in C# and renders the single active panel (.tab-content) as a sibling of thetablist(correct ARIA: atabpanelbeside thetablist). But daisyUI v5 keeps.tab-contentatdisplay: noneunless it immediately follows the active.tab— an adjacency that never matched this structure, so the panel stayed hidden once the basetabsstyles were present. A new scopedTabs.razor.cssforces the already-C#-selected panel visible.📦 Packages
DaisyBlazor.Components0.1.6DaisyBlazor.Charts0.1.6DaisyBlazor.Templates0.1.6@daisyblazor/tailwind0.1.6Full Changelog: v0.1.5...v0.1.6
v0.1.5What's Changed
Features
.nav-card*styling now ships in the package preset (styles/preset.css), and the stale::deepscoped 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.4What's Changed
Maintenance release — no
DaisyBlazor.Components/DaisyBlazor.Chartssource changes since 0.1.3. Rolls up the merged Renovate dependency updates.Dependencies
actions/checkoutto v6 by @renovate in #3actions/deploy-pagesto v5 by @renovate in #6actions/setup-dotnetto v5 by @renovate in #7actions/setup-nodeto v6 by @renovate in #8Full Changelog: v0.1.3...v0.1.4
v0.1.3What's Changed
Bug fixes
.ToString(_ci)leaking as literal SVG attribute text inLineChart(horizontal gridlines'x2) andDonutChart(guide-circler/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 asx2="588.ToString(...)"and SVG console errors. Added a regression test asserting no chart leaksToStringinto its rendered markup.Full Changelog: v0.1.2...v0.1.3
v0.1.2What's Changed
Features
NavCardsTitle— renders an optional heading above the nav-cards grid, mirroring the existingNavCardsslot and theQuickAccessTitle/QuickAccessButtonspairing. 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)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.