MagewirePHP

If you are familiar with Laravel Livewire v3, note these Magewire-specific implementation details:

• Component Discovery: Magewire does not use Livewire::component(). Components are discovered via Magento layout XML (e.g., <block class="..."/>) and resolved by ResolveComponents.
• Service Registration: Mechanisms and Features are registered via area-scoped Magento DI (etc/frontend/di.xml or etc/adminhtml/di.xml), not via global service providers.
• The app() Bridge: Calls to app('livewire') or app('redirect') are supported; Containers maps these to Magento DI bindings.
• Update Endpoint: AJAX updates are POSTed to magewire/update (a custom router), not /livewire/update.
• Template Compiler: The compiler is opt-in per directive area and can be extended via DI virtualTypes to allow themes to add custom directive namespaces.

In Magewire 3.0, updates are deferred by default. If you require the immediate update behavior found in v1, you must use specific modifiers.

wire:model

To make wire:model live (updating on every input/change), use the .live modifier:

- <input wire:model="query" />
+ <input wire:model.live="query" />

Entangle

Similarly, @entangle now defers updates. To match v1 behavior, use the .live or .blur modifiers:

@entangle('prop').live
// or
@entangle('prop').blur

Note: If you have applied the #[HandleBackwardsCompatibility] attribute to your component, plain wire:model and @entangle('prop') will be mapped back to their v1 live semantics automatically.

Magewire 1.x is no longer actively maintained and only receives security-related updates. For new features and regular bug fixes, you should upgrade to the latest major version.

Key migration areas include:

• Dependency changes
• The #[HandleBackwardsCompatibility] attribute (opt-in)
• Changes to wire:model semantics

For detailed migration steps, refer to the UPGRADING.md file in the repository.

Most Magewire 1.x components can continue working using a Backwards Compatibility (BC) layer. You must opt-in per-component by applying the #[HandleBackwardsCompatibility] attribute to your component class.

Without this attribute, the component will use Magewire 3.0 semantics. When applied, it flips a bc memo flag in the component snapshot to maintain v1 behavior.

use Magewirephp\Magewire\Features\SupportMagewireBackwardsCompatibility\Attributes\HandleBackwardsCompatibility;

#[HandleBackwardsCompatibility]
class MyComponent extends \Magewirephp\Magewire\Component
{
    // v1-style code keeps working
}

When using the WithPagination trait, you can manage multiple independent paginated sets within a single Magewire component by providing a unique name to the pagination methods.

• Default Paginator: Methods like getPage() and nextPage() without arguments operate on the default paginator.
• Named Paginators: Methods like getPage('name'), nextPage('name'), and previousPage('name') allow you to control a specific paginated instance identified by the string 'name'.

// Using the default paginator
$page = $this->getPage();
$this->nextPage();

// Using a named paginator
$itemPage = $this->getPage('item-page');
$this->nextPage('item-page');
$this->previousPage('item-page');

Magewire provides lifecycle hooks that are triggered when a page changes. The naming convention for these hooks depends on whether you are using the default paginator or a named one:

1. Default Paginator: Use the updatedPage(int $page) method.
2. Named Paginators: Use the kebab-cased name of the paginator in the method name: updated{KebabCasedName}(int $page). For example, a paginator named item-page triggers updatedItemPage(int $page).

// Triggered when the default page changes
public function updatedPage(int $page): void
{
    // logic here
}

// Triggered when the 'item-page' changes
public function updatedItemPage(int $page): void
{
    // logic here
}

The post-processors configuration allows you to enable or disable automated code styling and refactoring tools that run after the transformation process is complete.

Supported keys:

• rector: Boolean to enable/disable Rector for automated refactoring.
• php-cs-fixer: Boolean to enable/disable PHP CS Fixer for code style enforcement.

'post-processors' => [
    'rector' => false,
    'php-cs-fixer' => false
]