Advice for code & structure
Hi!
I'm currently developing my first app using Filament. My experience primarily lies in working with Laravel for smaller applications within startups and companies, where I focused on automating processes.
Recently, I decided to create a SaaS application using Laravel and discovered Filament in my research. I've been experimenting with Filament and have started integrating it into my SaaS boilerplate, particularly for core user panel functions like teams, roles, permissions, plugins, user/admin panels, and payment methods.
I've completed the Teams feature and its corresponding views in the admin panel. However, I'm unsure if I'm utilizing Filament optimally and have some questions. I would appreciate insights from experienced programmers:
I'm currently developing my first app using Filament. My experience primarily lies in working with Laravel for smaller applications within startups and companies, where I focused on automating processes.
Recently, I decided to create a SaaS application using Laravel and discovered Filament in my research. I've been experimenting with Filament and have started integrating it into my SaaS boilerplate, particularly for core user panel functions like teams, roles, permissions, plugins, user/admin panels, and payment methods.
I've completed the Teams feature and its corresponding views in the admin panel. However, I'm unsure if I'm utilizing Filament optimally and have some questions. I would appreciate insights from experienced programmers:
- Is it advisable to use Filament for an entire project? I find it very useful and want to incorporate it fully into my product. Are there potential issues with this approach, such as handling payments?
- Many developers seem to prefer custom Livewire components over resources for their models. Why is this?
- In what situations should custom Livewire components be used instead of resources? Can you provide an example?
- My TeamResource has 227 lines, including multiple functions like form, table, infolist, and some configurations. These seem like separate aspects of the same model, which makes me wonder if it's too much for one class. When should a class be split into smaller ones for cleaner code?
Or is this just the way how Filament should be used?
