[Bug]: Validation fails for options

[stian-scholtz-snappi]

What happened?

When attempting to save, filament throws a validation error.

How to reproduce the bug

When I have a schema containing:

GoogleAutocomplete::make('google_search') ->label('Search Google') ->autocompletePlaceholder('Search for an address on Google Maps') ->countries([ 'ZA', ]) ->columns() ->withFields([ TextInput::make('street_address') ->extraInputAttributes([ 'data-google-field' => '{street_number} {route}', ]), TextInput::make('suburb') ->extraInputAttributes([ 'data-google-field' => 'sublocality_level_1', ]), TextInput::make('city') ->extraInputAttributes([ 'data-google-field' => 'locality', ]), TextInput::make('postal_code') ->extraInputAttributes([ 'data-google-field' => 'postal_code', ]), Select::make('province') ->options(Province::pluck('name', 'id')) ->extraInputAttributes([ 'data-google-field' => 'administrative_area_level_1', ]), TextInput::make('latitude') ->extraInputAttributes([ 'data-google-field' => 'latitude', ]) ->hidden(), TextInput::make('longitude') ->extraInputAttributes([ 'data-google-field' => 'longitude', ]) ->hidden(), ]),

I get:

Filament failed to validate the [data.deliveryAddress.google_search.google_autocomplete_google_search] field's selected options because it did not have an [options()] or [getOptionLabelUsing()] configuration. Please use one of these methods to inform Filament which options are valid for this field.

Package Version

4.0.0

PHP Version

8.4

Laravel Version

12.0

Which operating systems does with happen with?

No response

Notes

No response

[stian-scholtz-snappi]

I am not sure if this is the correct fix but after a quick inspection, I was able to have the validation pass by doing:

->options(fn($state) => [$state])

This is on the buildSchema function inside Tapp\FilamentGoogleAutocomplete\Forms\Components\GoogleAutocomplete

This won't work if the user did not actually search and select an option because null is not allowed as valid option for validation. Hopefully this helps.

[aotearoait]

I can report this same issue. Only difference between my code and above is I am wrapping in a section with a relationship, but exact same error.