Andreas Reinhold / reiniandClaude Opus 5
fb7007c976
tests / feature (8.4) (push) Successful in 2m0s
tests / feature (8.5) (push) Successful in 2m0s
tests / browser (chrome, chromium) (push) Failing after 8m3s
tests / browser (firefox, firefox) (push) Failing after 12m58s
tests / browser (safari, webkit) (push) Failing after 13m8s
Tailwind left the stack in 2.0.0, but the package still carried about 330 mentions of it. What the guard's Tailwind detection protected — a class that compiles to nothing — is now protected by a check that does not care where a dead class came from. DesignGuard: about 500 lines of Tailwind tables, scales, palettes and "2.0.0 replacement" hints give way to one check — a class a view or PHP file writes that neither the application's stylesheets nor the package's own declare. It catches a utility of any framework, a typo and a class whose rules were deleted alike, so it also found two classes ReStride draws nothing with. A stylesheet has to be in reach for it: the `.css` files among the scanned paths, or what the `missingStylesheets()` entry imports. The class reader no longer mistakes an array index for a class list (`$block['base']`), and it reads the array a class helper is given, where it read nothing before. The package's own three Tailwind self-guards go with it. Only their one unique check stays, as a test of its own: every `matchMedia` width in resources/js is an M3 breakpoint. The pagination views are `material.blade.php` and `simple-material.blade.php`; only Laravel's and Livewire's default theme names ever made them `tailwind`. The provider sets `Paginator`'s default views and switches `livewire.pagination_theme` to `material` when it is still Livewire's own default, so no application can forget the config; a theme an application chose, and a component's own `$paginationTheme` or `paginationView()`, still win. The rest is prose: the layer-order guidance for an application that still builds Tailwind, the Tailwind wording in the README, the Boost guidelines and the development skill, and about 25 "this used to be a Tailwind utility" comments, along with every "plan step NN" pointer into a gitignored folder. The reset keeps its credit, and NOTICE now carries it too. Feature suite 1159 passed, Chrome browser suite 299 passed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
45 lines
2.1 KiB
PHP
45 lines
2.1 KiB
PHP
<?php
|
|
|
|
use Illuminate\Support\Facades\Route;
|
|
use NoNameWeb\LivewireMaterial\Http\Controllers\ShowcaseAssetController;
|
|
use NoNameWeb\LivewireMaterial\Http\Controllers\ShowcaseController;
|
|
use NoNameWeb\LivewireMaterial\Http\Controllers\ShowcasePageController;
|
|
use NoNameWeb\LivewireMaterial\Http\Controllers\ShowcaseSymbolController;
|
|
use NoNameWeb\LivewireMaterial\Showcase\Sections;
|
|
|
|
Route::get('/', [ShowcaseController::class, 'index'])->name('showcase');
|
|
|
|
Route::get('symbols.json', [ShowcaseSymbolController::class, 'index'])->name('symbols');
|
|
Route::get('symbols/{style}/{name}.svg', [ShowcaseSymbolController::class, 'show'])->name('symbol');
|
|
|
|
// The showcase's own stylesheet (all.css, showcase.css, the application's scheme), long-cached under
|
|
// the hash of its own content, and the two package folders its relative url()s point into: it sits
|
|
// in assets/css/ so `../fonts/…` and `../svg/…` land on the asset route, which it precedes.
|
|
Route::get('assets/css/showcase.{hash}.css', [ShowcaseAssetController::class, 'stylesheet'])
|
|
->where('hash', '[0-9a-f]+')
|
|
->name('stylesheet');
|
|
Route::get('assets/{path}', [ShowcaseAssetController::class, 'file'])
|
|
->where('path', '.*')
|
|
->name('asset');
|
|
|
|
Route::view('shell/{page?}', 'livewire-material::showcase.shell')
|
|
->whereIn('page', ['inbox', 'starred', 'sent', 'drafts', 'travel', 'receipts'])
|
|
->name('shell');
|
|
|
|
Route::get('errors/{code}', [ShowcasePageController::class, 'error'])
|
|
->whereIn('code', ['401', '402', '403', '404', '419', '429', '500', '503'])
|
|
->name('error');
|
|
Route::get('mail', [ShowcasePageController::class, 'mail'])->name('mail');
|
|
|
|
Route::get('search.json', [ShowcaseController::class, 'search'])->name('search');
|
|
|
|
// The Layout section's three canonical layouts, each a page of its own rather than an
|
|
// anchor on the Layout section's Overview (`{section}` below).
|
|
Route::get('layout/{page}', [ShowcaseController::class, 'layout'])
|
|
->whereIn('page', ['list-detail', 'supporting-pane', 'feed'])
|
|
->name('layout');
|
|
|
|
Route::get('{section}', [ShowcaseController::class, 'section'])
|
|
->whereIn('section', array_keys(Sections::all()))
|
|
->name('section');
|