odrotbohm

odrotbohm, 15 days ago

@frankel The one way to pass parameters is as… drumroll as parameter. 🙄🤷‍♂️

odrotbohm, 15 days ago

@frankel There’s just no „x ways“ to transfer parameters. There’s one. Because HTTP knows exactly one concept of a request parameter. Except you deliberately misinterpret what „a parameter“ is and tunnel it through other mechanisms. Which is abusing the protocol.

odrotbohm, 15 days ago

@frankel Yes.

odrotbohm, 15 days ago

@frankel I am not a fan of posts that misrepresent what they’re doing in their titles. Just as the original post it lists different ways to pass any kind of data but speaks of „passing parameters“. It feels like folks want to deliberately not understand the thing they claim to talk about. Words have meaning. Your post might be fine in general. But it’s riding a broken horse.

odrotbohm, 1 month ago

@scy It doesn’t. If in doubt serve the entire page, HTMX is gonna swap out the page and it still feels snappier. From that on, you might leverage your template engines ability to render and serve partials, but that’s an optional albeit pretty common approach.

odrotbohm, 1 month ago

@scy You asked a generic question, you get a generic answer. 🙃 doesn’t have to be a template. What matter is whether you can render snippets of HTML. A chat sounds like an easy enough todo thing as it’s basically appending divs. HTMX has native support for SSE, so depending how your server stack can deal with those, you should be able to get away without any custom JavaScript.

odrotbohm, 1 month ago

@scy Out of band swaps is what you’re looking for. Those allow you to send multiple partials that HTMX would put into the right place. You could return a single chat message besides some other div with an event (just make them sibling elements with the proper hx:swap each) and HTMX takes care of the rest. IIRC replace by ID is the default.

odrotbohm, 1 month ago

@scy I was replying to the „does it need to be tailored to HTMX“ part. You didn’t mention anything about a chat in the first post either, which is a very specific use case. OOB swaps are a first-class concept. Returning exactly the elements I want to have updated feels pretty natural to me.

odrotbohm, 1 month ago

@scy I think part of the challenge is that you conveyed two questions at once. A broad one (“What do you use it for?”) and a very specific one (“how don’t solve this one special thing for my chat app?”). That’s hard to respond to on social media.

On the former: I’ve built pretty complex dashboards for a commercial product in the SBOM space, some health care related CRM-like UI and some advanced examples primarily focusing on integrating micro-frontends.

odrotbohm, 1 month ago

@scy It feels like you’re overthinking it a little. The server sends HTML, you send the server forms, state is in the URI, nowhere else. If you think in these constraints (the constraints of the web essentially) things usually fall in place easily.

odrotbohm, 1 month ago

@scy @pa You’d send a form with the data to be changed, the server renders all elements that need to be replaced with new data. You return those to the client and HTMX replaces all elements you send. No custom JavaScript required.

odrotbohm, 1 month ago

@scy @pa I see. That “change username“ functionality existed before? How did you handle that on the server?

odrotbohm, 1 month ago

@scy @pa HTMX really plays to its strengths when you can both handle form submissions and produce HTML. It’s the antidote to the client messing with JSON and turning this into HTML eventually. I guess with a constrained server-side, HTMX is not of much help.

odrotbohm, 3 months ago

@shochdoerfer @majug Modulith! ☝️😬

odrotbohm, 3 months ago

@shochdoerfer Nice! Java has this for records. I’ve heard it’s coming for plain classes, too, but it looks like you got there first! 🙂