https://htmx.org logo
Powered by
# htmx-general
  • p
    I can see good arguments for either approach. My template building process caches whatever doesn't involve dynamic data. So I think it's relatively cheap on the server-side to grab the "built" template from RAM, populate the data (and run the template conditionals/loops/etc), then extract 1 or more DOM nodes by id.
  • t
    I like it. Parsing html is pretty cheap. A stop-gap solution I'm currently using is to just request the entire page and 
    hx-select
    specific ids, which is technically slower than returning just what I need, but not by any noticeable amount (couple microseconds). Doing the hx-select server-side would at least save bandwidth.
  • m
    hx-select-oob
    in the next release btw
  • p
    Ooh... nice!
  • t
    Meaning you could ignore certain oob swaps?
  • m
    You can use 
    hx-select-oob
    to pick out content from the server you want selected for an out of band swap outside of the "normal" 
    hx-select
  • m
    normal
  • m
    lol
  • m
    lmao
  • t
    ooooh
  • t
    So you don't have to specify oob on the returned html
  • t
    That's gonna come in pretty clutch for a thing I'm working on
  • t
    next release when?
  • b
    I was experimenting with something in this realm. All my templates are split up, but using the name I would use in BEM (the css system), e.g. 
    cpnt-recipes__food-entry-form.ejs
    . Then I had the same idea as you cp-sean of adding a third param to the render fn with a list of templates to render, wrap in an oob, and send along with the main template It worked out really well! BEM turns out to be a fantastic naming convention for chopped up templates, I think
  • p
    That's very cool. Seems like a number of us are rowing in the same direction here.
  • p
    Btw, in case anyone is interested, this is the Mongoose/Express/HTMX framework I've been working on: https://www.sanejs.dev
  • t
    mongoose, express, htmx... The "Meh" stack.
  • p
    Exactly!
  • t
    meh, this will do
  • t
    Perfect
  • c
    is the assumption here that a users will have server middleware in place to prevent anyone arbitrarily requesting all unprotected content on the server?
  • m
    i don't know if there were any assumptions, I just needed it for a project I was working on
  • c
    hi guys, have you ever encountered a problem with browser cache? when I do an action which returns HTMX response (in this case filtering catalog of products, which returns products and updated filters from API) then go to product detail and come back using back button, the request gets served from disk cache. In result the page is empty with no content in head, footer etc. just the HTMX part response displayed - which obviously breaks stuff as the css is missing
  • w
    I know you all know this already, but I just gotta say that Response Header 
    HX-Trigger
    is flippin' awesome! I've been using it, but in this Post method I just finished needed to fire three different preexisting client side events (close modal, update content section, fire a success toast) and so I just dropped all three event names into Response Header and off I go 😃
  • g
    I was going to reply to a previous comment about this same thing. Response headers are an easily-overlooked gem of htmx. HX-Trigger, HX-Retarget, and HX-Push-URL are magic, and have made a huge difference in the work I do 🙂 Three cheers for @mysterious-toddler-20573 and the htmx meme army!
  • w
    agreed! @mysterious-toddler-20573 is making our work a cake walk!! (especially coming from a world of Asp.Net WebForms). hip-hip-hooray^3
  • m
    thank you it is very edifying to hear it is helping 🙂
  • h
    hey it looks like eleventy is gearing up for a big update: https://github.com/11ty/eleventy/tree/v2.0.0-canary.11
  • h
    when that drops any objections to upgrading the docs
  • h
    I can't build them locally w/ node sass
1...703704705...1146Latest