style: unify all action buttons to the canonical grayscale chrome - #326
style: unify all action buttons to the canonical grayscale chrome#326fabiodalez-dev wants to merge 2 commits into
Conversation
Legacy views still used per-view accent colors (blue/green/indigo/purple/ orange/amber/cyan) for their action buttons, drifting from the canonical palette used across libri/autori/editori/prestiti. Recolour every genuine action button to the shared chrome: - primary -> bg-gray-800 text-white hover:bg-gray-700 - secondary -> bg-gray-100 text-gray-900 border border-gray-300 hover:bg-gray-200 - danger -> bg-red-600 text-white hover:bg-red-500 Only interactive elements (buttons and action links, all carrying a hover state) are touched. Semantic colours are left intact: status badges, alert boxes, calendar legend dots, stat cards and icons keep their meaning- bearing colours. 58 buttons across 12 views, class-only swaps (59/59 diff), no markup or logic changes.
|
Warning Review limit reached
Next review available in: 41 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (11)
📒 Files selected for processing (6)
📝 WalkthroughWalkthroughLa modifica uniforma i colori dei pulsanti nelle viste amministrative, dashboard, catalogo, prestiti e utenti. Le azioni, gli identificatori, i dati e i flussi JavaScript restano invariati. ChangesPalette delle viste
Estimated code review effort: 1 (Trivial) | ~5 minuti Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
Unify every action button across the legacy admin/detail views to the canonical grayscale chrome already used by
libri,autori,editoriandprestiti.Legacy views (dashboard, plugins, updates, pending loans, integrity report, bulk-enrich, user/author/publisher lists, book detail, loans list, user detail) still coloured their action buttons with per-view accents — blue, green, indigo, purple, orange, amber, cyan. This drifted from the shared palette and made the UI look "almost right but off".
Mapping
bg-gray-800 text-white hover:bg-gray-700bg-gray-100 text-gray-900 border border-gray-300 hover:bg-gray-200bg-red-600 text-white hover:bg-red-500Scope & safety
59 / 59diff, no markup or logic changed.hover:state (buttons and action links).hover:(none) and anybg-*-100 text-*-800badge removal (none).Verification
php -lclean on all 12 files.Summary by CodeRabbit