Writing Software Design Description (SDD) for Filament-based systems
Hello, im currently taking a subject in uni where i need to create the srs (software requirement specification) and sdd (software design description). I plan to develop a filament-based system to cut off the development time. In the sdd, there are sections where we need to create a package diagram to illustrate the folders and its files. Usually for the subject the lecturer expect to see the usual folders - Model, Controllers, and views. How do i do this for filament-based systems? When i explained about the Filament Resource the lecturer said it is equivalent to view files. How do i illustrate the backend process for filament-based systems?
7 Replies
I tried to explain that a Filament Resource actually does everything for us but he said there must be a controller somewhere. Please enlighten me
Btw the lecturer is experienced with Laravel, he just heard of Filament when my group introduced it to him.
your lecturer is wrong
do you understand livewire?
livewire is basically the controller in filament
and livewire renders views
filament resources are a separate entity to a controller or a view, they configure those controllers
so you could say that resources are a form of configuration
you see Create Edit and List page classes? those are the controllers
okay thanks. will try explaining it to him tmrw
Well he is not wrong if pages are the controllers 😅
i said that in response to "Resource the lecturer said it is equivalent to view files"
Okay that makes sense. Although I understand what he means. They control the design/layout via the form/table builder 😅
i see them as a translation layer before views
as i said, configuration that then gets interpreted by the view