FilamentPHP v4
Opened this issue · 4 comments
Hi,
Great package. It seems like filament's new changes messes with the AI models' predictions. Specifically:
- Layout components now reside in Filament\Schemas and not in Filament\Forms anymore. So the AI models all either figure it out and then change EVERYTHING to Filament\Schemas including the normal input components that are still under Filament\Forms, or sticks with Filament\Forms.
- On resources, $navigation* properties used to just be ?string. Now it is string|BackedEnum|null and all the models get that wrong every time.
- On tables, ->bulkActions() is now ->toolActions(), and ->actions() is now ->recordActions().
Also, resources are now structured:
- app/Filament//Resources/ResouceName.php
- app/Filament//Resources/Schemas/*.php containing resource form schemas
- app/Filament//Resources/Pages/*.php containing resource pages
- app/Filament//Resources/Tables/*.php containing resource tables.
- app/Filament//Resources/RelationManagers/* containing resource linked relation managers
Can you please include this in the instructions when you detect Filament V4?
And there is missing complete components documentation in filament here: https://filamentphp.com/docs/4.x/components/overview
u can solve this issue by adding a rules for claude.md to use the new defections of filament v4
u can solve this issue by adding a rules for claude.md to use the new defections of filament v4
Thanks, that is what we do now. I posted here because it would be nice if that came "out of the box" every time we install boost. I will completely understand if it is not in the scope of the project, as this will only be an issue until the AI models learn more about Filament v4. Just thought I will take a chance on having it in the standard instructions.
u can solve this issue by adding a rules for claude.md to use the new defections of filament v4
Could you provide us with those rules?