@User are you using a python framework?

Not yet, but planning on fastapi.

I am building a website for a friend, with some sales stuff, maybe a chat, and I want the project to be low maintenance six months from now.

which means as few external deps as possible 🙂

FastAPI can use Jinja templates, so you'll be using that to build your html strings

I have tried building something in .Net + React only to return to it six months later and finding out my C# version had been deprecated and the frontend could no longer build.

Ooh, now you are using fancy words I do not understand 😄

(I've dropped down a layer to Starlette instead of FastAPI as it has a load of things that I don't need)

https://fastapi.tiangolo.com/advanced/templates/?h=jinja and https://jinja2docs.readthedocs.io/en/stable/ Basically you'll pull the info from the DB, then pass it to the template, which will do all the looping etc to create what you want to send to the browser

Do you agree with this? I might need websockets for the chat module.

Ah, sorry I read it wrongly, seems like that is the feature list of Starlette.

Then I do not know what FastAPI offers 😛

Mainly API stuff. Though more people use FastAPI vs Starlette, so you'll probably be able to get more help on the FastAPI Discord instead of the Starlette (encode) Gitter.

(I really should flesh out my toy framework)

I have a little bit of experience with FastAPI, so I am going to go with that for now. Complexity budget and all that jazz.

But this seems to be a very helpful channel, so cheers to that!

FastAPI is perfect - I started with that.

+1 for a framework. I'm finishing up a project in Flask right now and it's been a joy

The only reason I suggest using whatever your back-end's native HTML generation uses is that there are a lot of "gotcha"s with HTML. That generation will likely guide you into writing it in a way that will produce valid HTML, whereas string concatenation will only work most of the time. (Escaping can easily become a security issue, but escape too much and you end up with "view source" without having to right-click... LOL) Since you've mentioned that you're targeting Python, that's one language ecosystem where I have very little experience. I would expect that the principles carry over, though; if you can write a template, then pass an object to that template to render HTML, that will be much more robust than doing the concatenation manually.

I'd recommend asking in #864934037381971988 as well - plenty of python people there even if you're not using django

#python-htmx because we have so many starlette people here

🐍

Hello, brand new user of htmx and looking to build a form that does server side validation, and if successful move onto a next screen. My first thought is that to show validation, I would like to leave the form in place, and target a different div with the validation content. It would seem the hx-target is not able to be specified as a response header from the server so the html fragment is going to need to include the entire form elements in additional to the validation message right? Is this how others are handling this? Is there any way to specify a different target on the server side?

I see this issue https://github.com/bigskysoftware/htmx/discussions/770

Yeah - I think you'll have to return the form as well. You can also use an oob-swap to target where to put your validation errors.

“… escape too much and you end up with view source” 😂👌 Yup, much better to use something which takes care of the heavy lifting (read: nitty gritty) of that stuff 👍

The HX-Retarget header was added in the latest version https://htmx.org/posts/2021-11-22-htmx-1.6.1-is-released/

Hi @gifted-airline-5816 and welcome! Like @bland-coat-6833 said, have a look at https://htmx.org/attributes/hx-swap-oob/. Another approach that is perhaps simpler, but definitely a bit more coarse-grained, is to expand the replacement target to include both the form and the validation errors. If you’re worried about performance because it’s more content getting swapped, I’d encourage you to try it out first and see, you might be pleasantly surprised. Although I feel you on wanting to keep things tight and swap as little as necessary… it comes down to style and preference. I found that keeping things a bit more coarse grained helps maintainability in the long run, but there’s always exceptions! As @most-jelly-15242 just said, hx-retarget might also be an option

Thanks! I will give HX-Retarget a try.