@KarolZ 🔥

🔥 Lets blaze 🔥

@asathler Sweet, yeah feels so much cleaner to have it right next to the html that will eventually be rendered.

@hugoferreira Thanks for the support! This is one of those tricky things as a creator. I want to make everyone happy, but I have to do what I think is best, otherwise, the project will get stale and I won't want to use it myself.

Livewire has actually never been MVC in the sense that there are no controllers. It's just a single component with a single view and multiple actions. If when you say MVC, you mean: separate file for php and separate file for Blade, the new multi-file components offer that.

I'm sure I don't fully understand your situation, but like you said, we are still supporting class-based for cases like yours or when people simply prefer it.

Cheers!

@nerisonpitogo that's right!

@skoTner Wow, so cool to hear that these tools have leveled up your team! What a kind comment to read. 👊

@justamoose - that's very kind. Thanks!

@azizabbas - thanks! great to hear!

@hellofromsteve haha, that was one of my hopes, that people would see other Livewire things in general here that they can use in their apps

@GrantJohnson thanks for the feedback. you got it!

@thenet thanks! enjoy!

@guilhermepolicarpo woohoo

@hubertkoy haha, those are definitely big ones. by far the hardest things to build in v4

@alecgarcia awesome, good luck!

@nerisonpitogo hahha understandable. both are there for you

Amazing feature! Thanks Caleb ❤️

Yeah, I was pleased by multi files structure and now.... I'm in love!

@javedurrehman exactly

@javedurrehman absolutely

@asathler haha what fortune!

@jlcara depends on the use-case. for simpler tables, I'd probably start there yep

@danielhe4rt love to hear it! A lot of thought went into it 👌

0:04 "Here's another little Diddy for ya" 😂 Loving the new features and the easily followable demos!

Dude! This is awesome!

@AntV yeah, most people don't need volt anymore. maybe i'll remove from v4 docs

@sacha-meunier hmmm not a bad idea!

@shaungbhone yeah, you have to get a feel for it, but once you do you can mix and match techniques to do pretty crazy things

@DaemonKeen ❤️

@medcharrafi 🔥

I believe Test file should be in the same directory with related files. Easy to read and easy to manage.

@OsamaElnagar 🙌

@thesnakebite fixed in 4.0.1

@Darkdawg thats pretty interesting!

Amazing! LV4, although same script exactly.

@sean2025 Awesome, thanks! Music to my ears!

Holy wire, livewire 4 is a crazy dream for the solo developer ⚡️

amazing caleb!

@Weasel - mmm yeah I could see that. all wire: directives have always been JS actually. We just didn't really advertise that to avoid confusion like this. Most wire: directives are actually the equivalent Alpine directives under-the-hood (just with the scope of $wire provided automatically if that makes sense)

Good feedback that wasn't obvious to me though, thanks

@andrewmenich Mmmm can you submit a github discussion bug with the single file component source so I can pull it down and test? We'll get that fixed in short order!

@OsamaElnagar Nice! Curious how many people choose the MFC approach over the SFC one.

@OsamaElnagar ⚡

@OsamaElnagar you got it!

@wikorl Not really right now. AI is your best bet. It's kind of a hard thing to automate because of all the potential customizations people might have in their class-based components. But maybe I should attempt like a 80% of components will work with this kinda solution.

@FrankMawn Yep! I wanted people to take advantage of all the LW4 goodness without having to buy-into a completely different paradigm

@mewtonium thanks mate! lets gooo

@bernig Welcome!

@willeums You're welcome!

Yo you and yours @Jordan_Acentrix ❤️

@PrinceMinky Wew!

@iamputhea FINALLY