InSeriousNeedOfHelp
How to disable button after performing the action
And what about disabling a form component after it's value is compiled for the first time? If I compile it and it uses this kind of function
->disabled(fn ($state) => !!$state)
to get disabled, it's value never reaches the save function of the form😅4 replies
Form actions must be an instance of Filament\Actions\Action, or Filament\Actions\ActionGroup.
So I cannot mix and match the suggested classes, as one requires the I would assume, correct one: Filament\Forms\Components\Actions\Action but the mount function breaks if the object is not either a Filament\Actions\Action, or Filament\Actions\ActionGroup
23 replies
Form actions must be an instance of Filament\Actions\Action, or Filament\Actions\ActionGroup.
I'm on 3.0.6, updated my composer this morning. The proble with using the suggested classes is that the "Actions" component for the form takes as input in it's constructor of type array<Action>, where Action comes from use Filament\Forms\Components\Actions\Action;
23 replies
Form actions must be an instance of Filament\Actions\Action, or Filament\Actions\ActionGroup.
One could argue that the code I'm using, being the same of the startup guide I previously linked, does not matter, bu anyways, here it goes:
https://gist.github.com/FraSaid/e1d10d38e277dec17b0887fcf563242a
23 replies
Error while trying to adapt a v2 pattern to v3
Yes patrick, that would be the case, anyway I followed your first suggestion and created multiple resources linked to the model, as to have more granular control over the forms. Still, how would someone register a page in the filament.admin.page route/namespace?
7 replies
Form actions must be an instance of Filament\Actions\Action, or Filament\Actions\ActionGroup.
this code:
Triggers that error. This is the same as the code at this page in the guide:
https://filamentphp.com/docs/3.x/forms/actions#adding-anonymous-actions-to-a-form-without-attaching-them-to-a-component
23 replies