Relationship select default value timing unclear in FilamentPHP Panels v3

Hydration Timing for Relationship Selects

In FilamentPHP Panels v3, default values are applied before the afterStateHydrated callback executes. When a form is initialized, Filament populates the state from the model (if editing) or applies the value defined in the default() method (if creating) before triggering the hydration hooks.

Lifecycle Execution Order

The general flow for a Select component tied to a relationship is as follows:

1. State Initialization: Filament checks for an existing model value. If none exists, it applies the default() value.
2. Hydration: The state is bound to the Livewire component.
3. Callback Execution: The afterStateHydrated closure is triggered, receiving the state as it exists after the previous steps.

Impact of Nullable Relationships

Whether a relationship is nullable or non-null does not alter the order of execution, only the value passed to the callback. If a relationship is nullable and no default is provided, afterStateHydrated will receive null. If a default is provided, that value will be present in the state when the callback runs.

Verifying State Timing

To inspect the intermediate state without modifying the Filament core, use Laravel's logging facility within the callback. This allows you to see exactly what the component holds at the moment of hydration:

Select::make('category_id')
    ->relationship('category', 'name')
    ->default(1)
    ->afterStateHydrated(function ($state) {
        \Illuminate\Support\Facades\Log::info('Hydration State: ' . var_export($state, true));
    })

Assumptions and Constraints

• Version Scope: This behavior assumes Filament v3, Livewire v3, and Laravel 10.x.
• Component Context: This timing applies to standard Panel forms. If the select is nested inside a Repeater or Wizard, hydration may occur in multiple passes as the parent components initialize.
• State Mutation: If you use $set within afterStateHydrated to change the value, ensure you are not creating a recursive loop that triggers further hydration events.

Diagnostic Detail Needed: Is this component located inside a Repeater or Wizard? If so, the hydration sequence may be deferred or repeated based on the parent's state management.