👍

here is the snippet:

and here is the response, regardless of what's selected:

p.s i tried to see whether data-hx-disable changes anything :/

Hi guys. I just learned Django and want to build a project like a clone of Reddit, is knowing Django + HTMX enough? I know HTML and CSS obviously and also JavaScript, but not react or other front end frameworks, except Bootstrap

Yes. You’ll get pretty far with just Django and HTMX.

Dodged a bullet with the vue man, lol. Good stuff.

Even Django alone would be enough, but if you want to have modern buttery smoothness, HTMX is the way.

there is a PR open for that 🤞

lol, was merged a few seconds ago 😄

Sorry but is anyone around that can help me understand how to debug or look at htmx logs?

I see in the docs it says to use "htmx.logAll();"

but I'm kinda new and I don't understand how to use this, or otherwise view htmx logs

Just call this method from your code or browser console

htmx will log every event after that

feelsbadman, theres no offtopic channel

🥲

oh...

😅

Is there a way to append

sse

messages to a html element, kind of how the

afterbegin

etc swap methods work? I'd like to receive

sse

events and append them to a list, rather than continuously replace the same element

So I use

afterbegin

with SSE. Sounds like you want

beforeend

to append to a list

I am trying to do hx-swap-oob but keeps on getting

htmx:swapError

, in response i am targeting the element by id and using the same id in base tag as well.

Might need to see what you’re sending back and what your htmx looks like.

Here we go https://linkode.org/#I8jFBtjNveWRh6JL7T0hm5

I am using 1.6.1 version, though i tried 1.8.0 but i think something else is off

last night I started thinking on something that had me worried. With HTMX, it seems a common pattern is to have the same route of the backend return two different payloads. If the

HX-Request

header is present on the request the response is only a fragment of the HTML, otherwise the response is the full page. This allows pushing the URL of the fragment to the navigation bar, and be able to share that URL with somebody, navigation back/forward, etc. All the goodness of having a working route for the full page, but that we can also use for partial updates. That let me to think that having two different responses defined only by the existence of a header disables two of the most basic HTTP cache mechanisms: the Last-Modified/If-Modified-Since and ETags. The browser cannot tell between a request with

HX-Request

and one without, so the response cannot be cached as the wrong one could be used (for example, the browser wants to load the full page but it has only the partial cached). Any thoughts about this?

Exmaple: create a simple page with a link to itself, and an HTMX powered button with an

hx-get

also to itself, but with a target of some div on the page. Then have a backend with that single page, either returning the full page or only the div, depending on the HX-Request header. Also, have that backend return a hard-coded last-modified on the response, and if it gets a If-Modified-Since return a 304. Then: 1. Load the page for the first time. 2. Click the button to trigger a partial update. The response will include a last-modified. 3. Click button again. The request will include a If-Modified-Since, so the backend will return a 304, and the cached partial response will load. 4. Now click the link. Again, the request will include a If-Modified-Since, so the backend will return a 304, and the cached partial response will load. Sad faces because we wanted the full html this time.

headers are part of the cache key, iirc