@zb9458
Thank you Lyle!! Your videos on HTMX and Django are amazing
@aafan.kuware
appreciating your work isn't just enough.
@Kabuki47
Thanks a lot for the explanation of the new HTMX's technique, sir!
@cabanford
Really nice and clean little clip. I like.
@hakanbilgin6875
Thank you for video
@NilotpaulNandi
Great vid, thanks man 👍
@seadude
So solid. Always clear as a bell. Thank you. Do you have a Django From Scratch series? Ideally, creating a CRUD app template. That would be awesome.
@AdnanNazirAhmed
Thanks, very useful.
@repotranstech
cool video as always
@AmoahDevLabs
Amazing gist. Thanks for sharing.
@JunHou-u4j
why are you so cool man
@MagnusAnand
💪💪
@plurallyplurally7948
How do you handle complex frontend state in HTMX? Do you have a video on that?
@kennyPAGC
I'm not sure what's the point of the hx trigger header here (which btw I don't agree with this design because I lean for a more clear backend and frontend separation) since it could all be done with the response status code.
@frameff9073
thank you
@djangodeveloper07
great video, but for delete an item, no confirmation box ? i don't think so it's a good practice to allow users to delete items on a single click without any warning ? does htmx provide any attribute for that ? second can we add loading/spinner like Deleting..... because on live sites, query can take 1 or 2 seconds to execute.
@codedjango
In SPA's removing any element from the frontend before the server response is received may cause side-effects if its existence triggers any other event on the frontend...so I think "optimistic updates" are a big "NO" ....I think spinner would give an appropriate message to the user and also not add to the errors in the frontend...but thanks to showcase the optimistic updates anyways..
@noob_coder001
Please make a video working with htmx and using datatables library . In addition use hx-boost="true" with the datatable elements for <a> tag its not working at the same time i got an duplicate datatable wrapper issue . 🥺 Please resolve my issuce man ,. :thanksdoc: Thanks in advance .
@bugbytes3923