Ti Theme Toolkit Laravel Package

Patch release

Removes the obsolete StaticPageResolverPatchTest left behind when the static-page resolver patch was dropped in v0.6.0. The test asserted a listener that no longer exists and failed against the released code.

Test suite + Pint lint are green.

No functional changes since v0.6.0 — see v0.6.0 release notes for the Livewire pagination override feature and static-page patch removal.

What's new

Livewire pagination override (new feature)

Themes can now replace Livewire's built-in pagination views with their own. Drop blade files into resources/views/livewire-pagination/ (e.g. tailwind.blade.php, simple-tailwind.blade.php) and the toolkit prepends that directory onto Livewire's livewire view namespace so they resolve first.

• Works for both numbered (paginate() → tailwind) and prev/next (simplePaginate() → simple-tailwind) paginators.
• Completely inert for themes that don't ship a livewire-pagination/ directory — no behavior change unless you opt in.

Why: Livewire's WithPagination trait calls Paginator::defaultView('livewire::<theme>') on every render, overriding any app- or theme-level pagination view. Prepending the namespace is the clean way for a theme to win that resolution without per-component paginationView() methods.

Removed: static-page resolver patch

Dropped registerStaticPageResolverPatch(). It was a workaround for an upstream tastyigniter/ti-ext-pages bug where static-page menu items resolved to the wrong page. That bug is now fixed upstream, so the patch — and its pages.menuitem.resolveItem listener — is no longer needed.

Upgrade notes

No action required. Themes already on the toolkit pick up the pagination capability automatically; add a resources/views/livewire-pagination/ directory to use it.

Added

• Storefront error views auto-wired — new AbstractThemeServiceProvider::registerStorefrontErrorViews() pushes the theme's resources/views onto config('view.paths') so Laravel's exception handler resolves errors::404 / errors::500 etc. to the theme's templates instead of TastyIgniter core's minimal fallback.
• Gated on ! Igniter::runningInAdmin() so admin-area exceptions keep rendering the admin error UI.
• No-op when the theme ships no errors/ directory.
• Also binds a composer that injects themeBrandStyle / themeNeutralStyle into errors.layout (the wildcard composer can't fire there — Laravel's exception handler renders outside any TI controller).

Themes previously hand-rolling this in their own SP can drop the duplication and let the toolkit do it.

Upgrade

composer require tipowerup/ti-theme-toolkit:^0.5.0