If that works, then I’d try a plain classless span inside the td with the hx attributes

Just wanted to check - we are planning to use a Bootstrap 5 based admin theme template and convert it to HTMX (with Java+thymeleaf). Has anyone used Bootstrap 5 based themes in HTMX. Does it work well ? First time doing htmx ..so a little unsure. https://github.com/creativetimofficial/soft-ui-dashboard

@mysterious-toddler-20573 @hundreds-cartoon-20446 Would you all be willing to make @hundreds-cartoon-20446 's extension that snapshots pages before JS effects occur as part of htmx's core or an officially included extension? It has helped me tremendously. https://gist.github.com/croxton/e2c33bd22591f9a5bd8c9d23a56c9edc

Yes, it does assumes you have

hx-swap="outerHTML"

for your boosted links and the returned response includes the hx-history element not just its innerHTML. I should probably make that clear, or maybe detect boosted link responses another way.

FWIW I really like the current behavior, perhaps including an example in a README or something would be useful as it is not immediately obvious (though the code is short / clean, so it can be understood with some digging)

Aha that's clever, works great thanks!

Just write code, not types 😉

You can't write big code bases without static analysis and documentation. That's a recipe for troubles. Bugs should be found by developers while developing, not by users on run-time.

You can’t, that’s why ~60% is run by php

Of the whole internet

I’m not saying static typing is not handy, I write most of the stuff in go and I find it super useful, but statically typed html? Seriously?

There is some line between static typing being useful and types stand in the way of your work

The fact that ~60% is run by PHP doesn't say it's easy, robust and scalable.

Not every app and website has to be like that

It’s like hypermedia, there is whole class of software that will run fine with just hypermedia instead of spa or other solutions.

Just pick the right tool for the job

Are you going to write new database engine? Then it makes to chose something more statically “typish”.

Why not? If I'm gonna use Web Components that's gonna be used many times in many HTMl templates, I need some tools to guide developers on how to use it and that will warn them when they misuse it.

Are you going to write new social network app for dogs with userbase equal roughly to ten? Then python could be a better choice.

I didn't say it.

You're right.

Man, I just asked for HTML static analysis tool, and without knowing which kind of software I want to write you said "write code, not types". 🙂

I’m sorry, maybe you’re right. Ive just been here, designing types instead of just writing code, that’s why I’ve wrote that.

For me it’s dead end. You can spend hundreds of hours trying to verify everything, so you have to put some line

For me typed html is behind this line

The types are already there. I just need a tool that is awerof the documention and will warn when misuse the code.

I have 80 developers that writes 100,000 lines of code of "just HTML". It won't be responsible of me to not providing them with a tool that will improve the correctness of their code, will make them more productive and will increase their DX.

Generally, all the code we write has types, including HTML (see MDN, it's all descriptinos of the types and protocols of HTML elements). It's just that some techonolgoes have tools that reflect and utilise it, and some are not and require the develoepr to click on many buttons in order to find a basic bug.

Is there a good way to build the equivalent of nested forms? Example:

<form hx-post="...">
    <input name="a" .../>
    <input name="b" .../>

    <input name="c" id="1234567" type="hidden" .../>
    <NESTED FORM>
       <input name="autocompleted" ... hx-post="..." hx-target="#1234567" />
    </NESTED FORM>

    <button type="submit">SUBMIT</button>
</form>

When the user types in the

autocompleted

(which is text), I want to hit an endpoint, which will be used to replace input

"c"

(

id="1234567"

) with a database ID. My main problem is that all of the form data (

a

b

and

c

) are sent to the autocomplete endpoint every time the user changes the autocomplete. This is making it hard for me to build an encapsulated auto-complete server-side component that doesn't get polluted by whatever elements surround it in a form. The other solution is for me to break out of HTMX and simply build this autocomplete in some other way (and hit a different, non-HTMX endpoint for the autocomplete results and use some JS to update form input

c

when the user makes a selection)

I think the answer is to use

hx-get

instead of

hx-post

in the autocomplete --

hx-post

includes form data by default while

hx-get

does not (I was using

hx-post

because the autocomplete can potentially create new database IDs if the user ends a new string value that has not yet been seen before -- but frankly this sort of idempotent is probably find to put in a

get

)