Видео

Say more, what’s a full tutorial mean to you?

@@youaskforit yeah you might be on to something with just using `ajax:success`. I honestly hadn’t considered that because I was thinking of approaches like Web Sockets or SSE. I’ll have to do some testing and maybe update the video.

I also do not understand why session? And not just return a div (or template) with an response from posting a form and add it to a dom to teigger an event?

That’s just a common patten in Laravel. It’s easy to push multiple messages into the session, and layouts are rendered from inside out, so you don’t have to carry your messages through multiple nested layouts to render them where you want.

I considered this more and decided it’s not a great solution: It could work in a very simple scenario, but as soon as you add validation to the mix things get complicated. If the request is invalid you don’t want `comment:changed` to be fired so you would have to inspect the response object in the `ajax:success` listener to determine what to do on the frontend. Setting a response header on the server isn’t a good option either because `fetch` can’t access headers on redirect responses. So I think triggering an event from the server is still the most bulletproof way to do this.

@@ima_crayon I haven't checked the alpine ajax source code, but does the library consider laravel's 422 response as ajax:success ?

Thanks! There’s written examples at alpine-ajax.js.org/examples/ but yeah I might try to record a few more too

@@ima_crayon Yes, I saw the examples before, they are very well explained! But unlike this video they are more micro UX patterns. Why this video is awesome is because it is a great example of how one would combine the UX patterns in those examples for a more broader page-level example (Blog page in this case). Future videos could cover examples like a "Product list page with category and price range filtering" and then maybe later extend it with a "Shopping Cart" popup, or how about a "Sortable Kanban style Todo list" page? Just throwing around ideas... Also, some constructive feedback for your video: a) I could not see the code sometimes because your face was in the way. Maybe move your face to a corner and make it smaller. b) Not everyone understands PHP in the back-end but everyone uses JS in the front-end so for more readability, it makes sense to keep it all JS for the back-end as well (e.g. NodeJS). This is not for me specifically by the way, I use Go in the backend. I just think everyone will relate more to the video that way. Please keep up the awesome work on Alpine AJAX! I'm really excited about it and I really think more exposure on how useful it really is will quickly increase adoption!