Hacker News Reader

> 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?

View on HN

That 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.

The 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?

How 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

You mean something like this? This does get a bit messier... https://htmx.org/docs/#oob_swaps

What 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!

Reply on news.ycombinator.com