https://htmx.org logo
Powered by
# htmx-general
  • g
    is one of those perverse incentives of the industry the fact that exponential complexity growth raises salaries and lowers the number of developers and therefore competition? we're unconsciously (or maybe sometimes consciously) ruining our own lives to keep other people away from our money.
  • p
    What's the easiest way to tell an hx-post which does not return any content (returns e.g. 204) not to make any DOM updates? (yes I can just use fetch() but wondering if there's an htmx way of doing it). e.g. I want to "ping" an update to the server, but don't expect or need to do any DOM changes as a result.
  • m
  • p
    hmm: seeing an odd behavior where a button "flickers" after sending an hx-post that receives a 204, but no such behavior with fetch(). Probably something wrong elsewhere (e.g. some inherited hx- behavior) but just wondering what the default expectation is.
  • p
    but if that's the expected result, it's probably something else going on.
  • m
    shouldn't flicker
  • m
    it's easy to get pretty blackpilled about the industry, I went through that back when I released intercooler and got a lot of noisy grief for it. On the other hand, things tend to cycle around in the industry and my sense is that things are beginning to turn (over a decade after I first released intercooler.js!) who knows. We'll see.
  • m
    Regardless, it's probably not worth getting too worked up over. Either the industry right itself, in which case great, or not, in which case we have an interesting tool that we can use that no one else really uses.
  • g
    i was daydreaming earlier about, what would a backend framework look like that was designed to work well with htmx?
  • m
    i think it's largely the backend frameworks we already have. The one thing I can think of helping a bit more would be a way to have partials within a template renderable, so you don't have to split them out. Something like:
    Copy code
    <div id="myOuterDiv">
     ...
     <div id="myInnerDiv">
       ...
     </div>
  </div>
  • m
    and the ability on the server side to render just the inner div w/ something like 
    someTemplate.myInnerDiv.render()
  • m
    then pulling out a partial for use in an htmx end point wouldn't involve creating another template file, which would be cleaner looking I think
  • m
    maybe
  • s
    backend framework.... one big part of this question: How to create HTML? I started to use format_html() in Django a lot. But f-strings in Python are simpler, BUT they don't support SafeString/conditional-escape. I had an idea how to improve python so that f-string like templating would be possible: https://github.com/guettli/python-custom-strings But I don't have much time to push this.
  • b
    dear all, how can i include csrf token in hx-get?
  • s
    By default hx-get does not include any parameters. You can use the hx-params attribute to change this. From: https://htmx.org/attributes/hx-get/ Does this answer your question?
  • m
    There's also hx-headers mentioned here https://htmx.org/posts/2021-2-13-htmx-1.2.0-is-released/
  • s
    Since http GET is readonly, you maybe don't need an csrf token. At least django only uses them for POST. And maybe you don't need a csrf token not at all, if you set cookie SameSite=LAX.
  • b
    Djang users I'll like to ask how is your experience with htmx Am really hoping this project will grow I am new or just trying htmx out But I really appreciate this project and I say bravo to the creator
  • m
    I just posted your question on twitter, hopefully someone w/ django experience will chime in. I know there is a project providing some helpers for django developers who want to use htmx: https://github.com/adamchainz/django-htmx
  • b
    Okay thanks
  • p
    @User to add csrf token to django, this works for me
  • p
    document.body.addEventListener('htmx:configRequest', (event) => { event.detail.headers['X-CSRFToken'] = '{{ csrf_token }}'; });
  • p
    add that somewhere on your base template and you should be fine
  • p
    as pointed out elsewhere, you don't need csrf token for GET requests.
  • p
    but that should cover all hx-* requests in any case
  • u
    @User Matt Layman has a take on that: https://dev.to/mblayman/how-to-use-htmx-in-django-49p3
  • f
    Hi there, yes, good post from Matt Layman. Another use case to "simulate" an SPA but without all the hassles. https://juliensalinas.com/en/htmx-intercoolerjs-django-nlpcloud/
  • b
    Thank you
  • r
    I will suggest implement turbolinks for simulate the SPA at 100% of the page 🙂
1...254255256...1146Latest