Package views now write <x-livewire-material::button>, so a configured prefix (which Blade spells <x-m::button>) and an application component of the same name can no longer break or shadow them. The showcase rewrites its examples to the configured prefix. Adds the README, and waits for the adaptive rail to hear a resize before the navigation tests press its menu button. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V9NnLxnPp8vaaurb3Z1MFy
17 lines
877 B
PHP
17 lines
877 B
PHP
<section id="pages" class="scroll-mt-24 space-y-6">
|
|
<h2 class="type-headline-md">Pages</h2>
|
|
|
|
<p class="max-w-3xl type-body-md text-on-surface-variant">
|
|
The error pages, raised for real so an app's own <code>resources/views/errors</code> still wins, and the Markdown mail theme
|
|
(<code>livewire-material::mail.theme</code>) on a sample mail, both in this application's scheme.
|
|
</p>
|
|
|
|
<div class="flex flex-wrap items-center gap-2">
|
|
@foreach (['401', '402', '403', '404', '419', '429', '500', '503'] as $code)
|
|
<x-livewire-material::button :link="route('livewire-material.error', $code)" :label="$code" variant="tonal" no-wire-navigate />
|
|
@endforeach
|
|
|
|
<x-livewire-material::button :link="route('livewire-material.mail')" label="Sample mail" icon="mail" variant="outlined" no-wire-navigate />
|
|
</div>
|
|
</section>
|