https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • t
  • t
    if you want to be pegged erb style - here you go https://ejs.co/
  • t
    pug is also available for js https://pugjs.org/
  • t
  • t
    but i think it's nuts
  • r
    pugs always enticing because less code, everything else there is more typing man
  • t
    less typing - pug,haml
  • r
    yup lol
  • t
    i like my curly braces and nunjucks and want to use it in my userscripts
  • s
    I'm happy with nunjucks. The thing that it is lacking is streaming support.
  • s
    Ultimately I would prefer having native rendering. Why use js engine for that - I don't see a point in that, since it's CPU-intensive task.
  • s
    There is marcojs. It supports streaming and does 90% of the work at compile time. But it requires a bundler. I'm not ready to add a bundler to the stack yet
  • s
    I will fight against bundlers till I die haha
  • j
    is there a way to stop a hx-vals from being sent? ive tried null and just returning nothing but that seems to send that value still
  • r
    I think there was "unset" value for this purpose?
  • b
    what do you mean by native rendering?
  • b
    I hate webpack, but I found esbuild to be pretty harmless
  • r
    Hi there. I'm using preload HTMX extension. Preloading works as expected, however when clicking the button after preloading has been done, the request is issued a second time. It does not hit a cache. Did I miss something?
    Copy code
    html
<button
  hx-get="{% querystring table.prefixed_page_field=table.page.next_page_number %}"
  preload="mouseover"
  hx-trigger="click"
  hx-target="#table-wrapper"
  hx-swap="outerHTML"
  hx-push-url="true"
>
  »
</button>
  • a
    Guys, how would one use: htmx:afterRequest? Planning to display a message after successful POST (200/201)
  • m
    are you sending the correct header to tell the browser to cache it? https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching
  • m
    you might want the example using `htmx:beforeSwap`: https://htmx.org/docs/#modifying_swapping_behavior_with_events
  • a
    @red-france-69804 adding https://htmx.org/docs/#caching
  • r
    Thanks! So if I understand, basically, I just need to inject the 
    Vary: HX-Request
    in all my requests to ensure caching occurs properly with urls that can load full pages AND htmx fragments. Right?
  • a
    yes
  • a
    also, your server must generate the right response caching headers
  • a
    otherwise, the browser doesn't know that it can cache that response
  • r
    Ok. I'm using Django and never managed caching headers manually. I was expecting that somehow the default behaviour was the right one. I may be wrong.
  • m
    typically application server responses from dynamic end points are set up not to cache, since their content is dynamic
  • m
    not familiar w/ how django works, but that's been my experience
  • r
    Thanks it's a lot clearer now. I'd suggest adding a small warning in https://htmx.org/extensions/preload/ doc to remind caching needs to be configured separately. I know this sounds obvious to most of you, but having never configured HTTP cache before, I was expecting preload config was the only thing I needed 😣
1...954955956...1146Latest