Ok, I think I understand, it will do the trick, thanks :)

Yes, you can definitely do a redirect based on the submitted value, but not quite the ease of use I would like!

When i send rendered HTML from the server back to the front for HTMX to pick up, i get an hx-swap error. In the HTML i have a table row, and also a

<div "hx-swap-oob="true"></div>

. I think it's because it's invalid HTML to have a table row and a div together in the response? When i remove the table row it works. Is this normal behaviour?

table parsing strikes again

if are willing to forego IE11 support, you can set

htmx.config.useTemplateFragments

to

true

and it should work 😑

This seems to me to be a perfect place for a little hyperscript glue. If it's a common request it could go in a cookbook. Off the dome:

<select name="url" hx-get="/" hx-swap="none" _="on change set my @hx-get to my value then htmx.process(me) then send redirect to me" hx-trigger="redirect">

Hello everyone! Can anyone please tell me how to put DOMSubtreeModified event to trigger using htmx?

I have a span html of which is changing. I need to trigger this change. Maybe it is possible to trigger change some attribute of it?

excellent idea! https://codepen.io/1cg/pen/PoQBLbj?editors=1000

Hah that is far more elegant, well done

just reduced 120 lines of code to 4 with htmx and some dry coding practices :] also improved functionality. couldn't be more happy.

Hello HTMX fans, I have a question that is probably language / framework agnostic so I hope I can ask it here. What is the best methodology / technique to use BOTH hypermedia / SSR via shipping html fragments and also a full JSON based API. Basically, I'm required to provide a JSON api for our users to hit using curl for whatever they want, but I also want the actual app to use HTMX. Ideally I'd like to find a way to combine these efforts without just basically writting 2x apps.

Also, @mysterious-toddler-20573 , you should really consider drinking some water, it is good for you.

😑 water lol

i think if you factor your domain logic into a model you shouldn't have too much redundancy. end of the day the JSON end points are probably going to be pretty different, using GraphQL or whatever, but pretty regular, so it shouldn't be that much work to maintain

As an example, here’s what works for me: I’m using mongodb as if it’s SQL Server. Each page in my admin tool has one primary query (

/users

lists all users,

/users/:id

details on a specific user,

/users/:id/posts

list all posts for a user, etc.) and other extraneous ones that help generate the HTML (authentication, lookup codes, etc). For these kinds of endpoints, I have two kinds of output templates: an HTML encoder (template) that generates the htmx fragment, and a JSON encoder that returns the primary query as JSON. You can determine which encoder to use with a URL (

/users

vs

/users/json

) or nn extension (

/users/1.html

vs.

/users/1.json

) or using the "Accept" request header. The "Accept" header is the most "RESTful" of the methods, but it has some drawbacks in terms of developer ergonomics. Every endpoint doesn’t need to have a JSON fork, just the big ones that support your API. This has worked out really nicely so far, though my need for the JSON endpoints has dwindled as I've dug deeper into the htmx/hyperscript ecosystem.

Having an odd one with loading a select 2 thing inside a boostrap modal. If I use a multiple select, everything works fine after messing around with some z-index values. However, a single select appears to work, but the search bar is not usable. As in, can't type into it. Figured someone might have run into something similar at some point around here?

Is "select 2" a proper noun? Do you think you could distill the issue into a codepen? Will be easier to directly help in that case

Hmm I did add a space there, it's select2. There's been quite a few talk of it around here, and I think it's such a specific issue that either someone by chance happened to see the same thing, or I'm just screwing something up somewhere.

Ah, I'm sure I've heard of it/seen it come up here but I haven't used it. Interesting bug tho

for future reference

I really like this approach (using content-type / accept), but my framework (FastAPI with Python) doesn't really handle content-type switches and custom renderers, I might have to build out something for that myself.

I'll try to write up a codepen tomorrow when I get back to that issue though. Got bigger problems to solve right now

You can actually support URLs AND “Accept” headers with something like a middleware to rewrite the URL.

You can write a bit of middleware for FastAPI to look at headers on the request and modify the response.

Well, benpate beat me to it.

By like 5 seconds 🙂

Glad I waited to say this second — @tall-dinner-62086 and @brainy-ice-92385 having the same color avatars broke my brain for longer than I’m comfortable admitting.