Complete the showcase and record Phase 10
tests / lint (push) Has been cancelled
tests / feature (8.4) (push) Has been cancelled
tests / feature (8.5) (push) Has been cancelled
tests / browser (chrome, chromium) (push) Has been cancelled
tests / browser (firefox, firefox) (push) Has been cancelled
tests / browser (safari, webkit) (push) Has been cancelled

Shows the plain tooltip on its own, checks that every component appears
in the showcase, and records the namespace change and the fresh
application check in the plan.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V9NnLxnPp8vaaurb3Z1MFy
This commit is contained in:
Andreas Reinhold / reini
2026-09-13 09:08:35 +02:00
co-authored by Claude Opus 5
parent 1e580c573e
commit cbf874a5a6
4 changed files with 42 additions and 2 deletions
+18
View File
@@ -578,6 +578,24 @@ pages and the mail theme by an agent in its own worktree. What changed from the
(drift test green); README (install, CSS/JS wiring, scheme, theme, prefix, showcase,
guard, Docker ordering note); tag `1.0.0`.
**Phase 10 is done (2026-09-13).** What changed from the step above:
- **The package's own views write `<x-livewire-material::name>`** for the components they use. Blade
spells a configured prefix `<x-m::button>` (not `<x-m-button>`, as the config first claimed), and
an unqualified `<x-button>` inside a package view would have broken under a prefix and been
shadowed by an application's own `components/button.blade.php`. A test scans every package view
(outside comments and the showcase's example heredocs) for unqualified tags, and the showcase
rewrites its examples to the configured prefix. The component path string stays
`__DIR__.'/../resources/views/components'`: Blade names the view namespace after its hash, and
compiled views keep that name.
- **A test checks that every component appears in the showcase.**
- **Verified in a fresh Laravel 13.31 application** (`composer create-project`, the package from a
path repository, the README's CSS, JS and layout, `material:scheme "#4f46e5"`, `npm run build`):
a Livewire page with an app bar, tabs, a card, a form with validation, a date picker, a dialog and
a toast works without console errors; `/material` and the 404 page render in its scheme.
- **Known gap:** `<x-datepicker>` has no clear button (`<x-timepicker clearable>` does); a date can be
emptied through its text input.
### Phase 11 — SealShare 2.0.0
Tracked in SealShare's `docs/plans/livewire-material.md`, after `1.0.0`.