Upgrade daisyUI to 5.7, remove daisyUI 4 leftovers and add a UI guard closes #597 #606
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
local-it/mitgliederverwaltung!606
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue/mitgliederverwaltung-597"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
closes #597
Description of the implemented changes
The changes were:
Upgrades Tailwind to 4.3.3 and daisyUI to 5.7.50, replaces all remaining daisyUI 4 classes, removes dead CSS and components, unifies icon sizes, and adds a source-scanning UI guard to
just ci-devthat fails on new daisyUI 4 classes, palette colors,data-confirmand raw modals beyond a documented exception list. A dev-only component showcase at/dev/componentsrenders the components in both themes.What has been changed?
Definition of Done
Code Quality
Accessibility
Testing
Additional Notes
Larger commits: the daisyUI upgrade (vendored
daisyui.js/daisyui-theme.js, ~1200 lines), the daisyUI 4 field replacement (18 files) and the icon commit (15 files) are mostly mechanical; the UI guard commit (~1400 lines) is the scanner intest/support/ui_guard.exwith its property tests.Visual check: before/after screenshots in both themes were compared; two upgrade regressions (Tailwind 4.3 default font stack, daisyUI 5.7 outline badge text) were fixed. The new fieldset spacing in the join form and the group/custom-field delete dialogs was verified by markup tests, not visually.