When I looked at the views (here's the link: views folder), it seems like they’re mixing traditional Blade templates with small Livewire components here and there, rather than going all-in with Livewire. The entry point for these routes tends to be a show.blade.php file, which centralizes the layout for the page.
Another thing I found curious is that the Http/Livewire directory is pretty flat (see it here: Livewire Directory). It doesn’t use a livewire folder inside the views directory like some other setups might. This got me thinking about how this might affect organization and scaling as the project gets bigger.
My Take on It:
I actually like the idea of organizing things by feature—it keeps everything focused and easy to find. And having that single entry point like show.blade.php makes the layout more predictable. If this were my own project, whether personal or for a company, I’d probably do something similar. However, I might lean towards using Volt instead of class-based Blade components because I like how everything stays in one place with Volt—it just feels tidier to me.
I’m also thinking about the approach of starting with a controller. It’s a good starting point, but the tricky part is deciding when to shift from Blade over to Livewire. Jetstream seems to mix actions with inline logic in places like DeleteUserForm.php, which can be pretty flexible. But it does raise questions about maintainability and where to draw the line between keeping things simple and being overly granular.
I’d love to hear how others are handling similar setups or any thoughts on where Jetstream could do things differently. What would you change if it was your personal/enterprise project? submitted by /u/Eznix86
[link] [comments]
0 comments:
Post a Comment
Thanks