3 ms·
> I got into situations where I needed to pass a bunch of data back to the rendering page and it got really messy. Could you not fetch that data separately fro
by mostlysimilar 3y ago
> I got into situations where I needed to pass a bunch of data back to the rendering page and it got really messy.
Could you not fetch that data separately from the patterns htmx provides and do some light parsing/rendering logic client-side?
- DoesntMatter22 3y agoThat data needs to go to the page itself. Like you need to pull data that is on the main page and send that data down to the modal form submission. That is tricky. Is it doable? Yeah, it can be done but it's really ugly at that point.
- a_subsystem 3y agoThe data was on the server at some point to begin with. How could it be tricky to put it somewhere just because $component is a modal?
- DoesntMatter22 3y agoHow could it be tricky to have html loaded on multiple different parts of the page? Do you think it happens automatically? You have to track all of it. It's a pain. You need to embed hidden inputs then need to capture them, send them off, The modal stays on the screen but the underlying page needs to change behind it. If you think that's easy then you'll love HTMX
- a_subsystem 3y agoYou mean something like this? This does get a bit messier... https://htmx.org/docs/#oob_swaps https://htmx.org/docs/#oob_swaps
- throwaway2990 3y agoWhat you’re explaining didn’t make much sense. Would like to see an example where it’s messy because I haven’t seen one yet. The ids changing is annoying tho!