Fix for bug #12602

[dmitry-udod]

Description

Fix for bug #12602

Screencast.2024-05-03.16.06.32.mp4

Visual changes

Nope

Functional changes

• Code style has been fixed by running the composer cs command.
• Changes have been tested to not break existing functionality.
• Documentation is up-to-date.

[danharrin]

I don't think this is a problem specific to wizards. It happens whenever a dynamic schema is involved, and my advice is usually to use afterStateUpdated() on the component that determines the schema to $set() the field values for the new fields. I do feel a bit weird filling the defaults after the form is first loaded, it could be unexpected behaviour.

Gonna need to leave this open while I consider it

[dmitry-udod]

@danharrin Hi! Sure. Just FYI, the problem here is that without applying default values for next step fields, we don't have this data at all. Please check the video.

Screencast.2024-05-03.16.28.14.mp4

[danharrin]

Yeah, so it's the same problem as something like this:

TextInput::make('test'),
Group::make(function ($get) {
    if ($get('test') === 'foo') {
        return [CheckboxList::make('test2')->options(['one' => 'One', 'two' => 'Two'])];
    }

    return [];
}),

Which is solved by:

TextInput::make('test')
    ->afterStateUpdated(fn ($set, $state) => ($state === 'foo') ?
        $set('test2', []) :
        null
    ),
Group::make(function ($get) {
    if ($get('test') === 'foo') {
        return [CheckboxList::make('test2')->options(['one' => 'One', 'two' => 'Two'])];
    }

    return [];
}),

[danharrin]

This solution is actually documented, so closing this