Mark
Mark
FFilament
Created by Mark on 12/22/2023 in #❓┊help
Undefined variable $canSelectPlaceholder using Select in Custom Field
I figured it out. I needed to change it over to kebab case. It still threw some errors about not being callable until I changed it out to a closure. Here's the final code:
<td class="w-1/3 p-0">
<x-filament-forms::select
x-model="row.fieldType"
:disabled="(! $canEditFieldTypes()) || $isDisabled"
:can-select-placeholder="fn(): bool => false"
:attributes="
\Filament\Support\prepare_inherited_attributes(
new \Illuminate\View\ComponentAttributeBag([
'x-on:input.debounce.' . ($debounce ?? '500ms') => 'updateState',
])
)
"
class="font-mono"
>
@foreach ($getFieldTypes() as $fieldType => $fieldTypeLabel)
<option value="{{ $fieldType }}">{{ $fieldTypeLabel }}</option>
@endforeach
</x-filament-forms::select>
</td>
<td class="w-1/3 p-0">
<x-filament-forms::select
x-model="row.fieldType"
:disabled="(! $canEditFieldTypes()) || $isDisabled"
:can-select-placeholder="fn(): bool => false"
:attributes="
\Filament\Support\prepare_inherited_attributes(
new \Illuminate\View\ComponentAttributeBag([
'x-on:input.debounce.' . ($debounce ?? '500ms') => 'updateState',
])
)
"
class="font-mono"
>
@foreach ($getFieldTypes() as $fieldType => $fieldTypeLabel)
<option value="{{ $fieldType }}">{{ $fieldTypeLabel }}</option>
@endforeach
</x-filament-forms::select>
</td>
2 replies
FFilament
Created by Mark on 8/16/2023 in #❓┊help
Rendering a component before the user menu on the header
I ended up upgrading to Filament V3 as part of the solution. I'll take a further look at it once the upgrade is done.
12 replies
FFilament
Created by Mark on 8/16/2023 in #❓┊help
Rendering a component before the user menu on the header
didn't make much of a difference though.
12 replies
FFilament
Created by Mark on 8/16/2023 in #❓┊help
Rendering a component before the user menu on the header
I sure did.
12 replies
FFilament
Created by Mark on 8/16/2023 in #❓┊help
Rendering a component before the user menu on the header
That's a thought.
12 replies