Foundation

Foundation is the permanent core of wire-core. It provides shared traits, base classes, icons, colors, and Blade components used by all other modules and packages.

Concerns (Traits)

Component Configuration

State & Behavior

Infrastructure

Action-specific

Closure Evaluation

All configuration methods accept both scalar values and Closures:

// Scalar
TextColumn::make('name')->label('Full Name');
 
// Closure — evaluated per record at render time
TextColumn::make('name')->label(fn (User $record) => "Name: {$record->name}");
 
// Closure with dependency injection
Action::make('edit')->hidden(fn (User $record, Table $table) => ! $table->isEditable());
// Scalar
TextColumn::make('name')->label('Full Name');

// Closure — evaluated per record at render time
TextColumn::make('name')->label(fn (User $record) => "Name: {$record->name}");

// Closure with dependency injection
Action::make('edit')->hidden(fn (User $record, Table $table) => ! $table->isEditable());

Base Classes

// All components use the static factory pattern
$field = TextInput::make('email');
$column = TextColumn::make('name');
$action = Action::make('delete');
// All components use the static factory pattern
$field = TextInput::make('email');
$column = TextColumn::make('name');
$action = Action::make('delete');

Icons

The complete Heroicons solid collection (324 icons, 20x20 viewBox) is bundled inline — no external dependencies, no extra package.

Blade Usage

<x-wire::icon name="check" class="w-5 h-5" />
<x-wire::icon name="trash" class="w-4 h-4 text-red-500" />
<x-wire::icon name="check" class="w-5 h-5" />
<x-wire::icon name="trash" class="w-4 h-4 text-red-500" />

PHP Usage

use NyonCode\WireCore\Foundation\Icons\IconManager;
 
$svg = app(IconManager::class)->render('check');
use NyonCode\WireCore\Foundation\Icons\IconManager;

$svg = app(IconManager::class)->render('check');

Available Icons

Every icon uses its canonical Heroicons name — the file name from heroicons.com (solid variant). Browse the full set there; a few examples:

academic-cap, arrow-down-tray, bars-3, chevron-up, cog-6-tooth, document-text, envelope, funnel, magnifying-glass, pencil, qr-code, trash, user, wrench-screwdriver, x-mark.

For IDE autocompletion you can reference icons through the Icon enum instead of raw strings:

use NyonCode\WireCore\Foundation\Icons\Icon;
 
Action::make('edit')->icon(Icon::pencilSquare);
use NyonCode\WireCore\Foundation\Icons\Icon;

Action::make('edit')->icon(Icon::pencilSquare);

Wire-friendly Aliases

A small set of short aliases map onto canonical icons for convenience:

Adding Custom Icons

You don't have to settle for the bundled set. Pick whichever approach fits — they all add to (or override) the defaults, and a custom icon is used anywhere an icon name is accepted (->icon('logo'), <x-wire::icon name="logo" />, …).

Icons are wrapped in a 0 0 20 20 viewBox, so design custom SVGs on a 20×20 grid for consistent sizing.

1. From a folder of SVG files (easiest)

Drop .svg files in a directory and register the path — the file name becomes the icon name (logo.svg → logo). No class, no boilerplate.

Via config (config/wire-core.php), great for app-wide icons:

'icons' => [
    'paths' => [
        resource_path('icons'),        // resources/icons/logo.svg => "logo"
    ],
],
'icons' => [
    'paths' => [
        resource_path('icons'),        // resources/icons/logo.svg => "logo"
    ],
],

Or at runtime, with an optional prefix to namespace the set:

use NyonCode\WireCore\Foundation\Icons\IconManager;
 
app(IconManager::class)->registerIconsFromDirectory(
    resource_path('icons/brand'),
    prefix: 'brand',                   // brand/logo.svg => "brand-logo"
);
use NyonCode\WireCore\Foundation\Icons\IconManager;

app(IconManager::class)->registerIconsFromDirectory(
    resource_path('icons/brand'),
    prefix: 'brand',                   // brand/logo.svg => "brand-logo"
);

2. Inline, by name

Register individual icons — paste a full <svg>…</svg> (the wrapper is stripped automatically) or just the inner <path>:

app(IconManager::class)->registerIcons([
    'logo'  => '<svg viewBox="0 0 20 20"><path d="M10 2 …"/></svg>',
    'spark' => '<path d="M10 1 12 8 …"/>',
]);
app(IconManager::class)->registerIcons([
    'logo'  => '<svg viewBox="0 0 20 20"><path d="M10 2 …"/></svg>',
    'spark' => '<path d="M10 1 12 8 …"/>',
]);

Reuse the same name as a bundled icon to override it.

Put either call in a service provider's boot() method so the icons are available everywhere:

public function boot(): void
{
    app(IconManager::class)->registerIconsFromDirectory(resource_path('icons'));
}
public function boot(): void
{
    app(IconManager::class)->registerIconsFromDirectory(resource_path('icons'));
}

3. A reusable icon set (advanced)

For a complete, swappable theme (e.g. a different icon style), implement IconSet and register the class in config under icons.sets. Sets registered here take priority over the bundled defaults:

use NyonCode\WireCore\Foundation\Icons\IconSet;
 
final class MyIconSet implements IconSet
{
    public function getPath(string $name): ?string { /* return inner SVG or null */ }
    public function has(string $name): bool { /* … */ }
    public function names(): array { /* … */ }
}
use NyonCode\WireCore\Foundation\Icons\IconSet;

final class MyIconSet implements IconSet
{
    public function getPath(string $name): ?string { /* return inner SVG or null */ }
    public function has(string $name): bool { /* … */ }
    public function names(): array { /* … */ }
}

// config/wire-core.php
'icons' => [
    'sets' => [
        'default' => DefaultIconSet::class,
        'custom'  => App\Wire\Icons\MyIconSet::class,
    ],
],
// config/wire-core.php
'icons' => [
    'sets' => [
        'default' => DefaultIconSet::class,
        'custom'  => App\Wire\Icons\MyIconSet::class,
    ],
],

You can also register a set at runtime: app(IconManager::class)->registerIconSet(new MyIconSet).

Regenerating the bundled Heroicons

The bundled paths live in the generated PHP data file packages/core/resources/icons/heroicons-solid.php, produced from the official heroicons npm package (20/solid SVGs, keyed by file name). Regenerate that file rather than editing icon paths by hand.

Colors

Tailwind CSS color abstraction — 7 semantic color names:

Action::make('delete')->color('danger');
BadgeColumn::make('status')->colors([
    'active' => 'success',
    'pending' => 'warning',
    'inactive' => 'danger',
]);
Action::make('delete')->color('danger');
BadgeColumn::make('status')->colors([
    'active' => 'success',
    'pending' => 'warning',
    'inactive' => 'danger',
]);

Each color resolves to Tailwind utility classes for bg, text, border, ring, and hover variants.

Support Utilities

Blade Components

Foundation provides base components under the wire:: namespace:

{{-- Icon --}}
<x-wire::icon name="check" />
 
{{-- Badge --}}
<x-wire::badge color="success">Active</x-wire::badge>
 
{{-- Button --}}
<x-wire::button color="primary" size="sm">Save</x-wire::button>
 
{{-- Dropdown --}}
<x-wire::dropdown>
    <x-slot:trigger>Options</x-slot:trigger>
    <x-wire::dropdown.item>Edit</x-wire::dropdown.item>
    <x-wire::dropdown.item>Delete</x-wire::dropdown.item>
</x-wire::dropdown>
{{-- Icon --}}
<x-wire::icon name="check" />

{{-- Badge --}}
<x-wire::badge color="success">Active</x-wire::badge>

{{-- Button --}}
<x-wire::button color="primary" size="sm">Save</x-wire::button>

{{-- Dropdown --}}
<x-wire::dropdown>
    <x-slot:trigger>Options</x-slot:trigger>
    <x-wire::dropdown.item>Edit</x-wire::dropdown.item>
    <x-wire::dropdown.item>Delete</x-wire::dropdown.item>
</x-wire::dropdown>