https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    mmm
  • o
    What was the name of the technique for extracting parts of a template from a single HTML template file? Document fragments?
  • m
  • o
    Oh yes that! Thank you!
  • a
  • m
    PR?
  • m
    how do folks feel about this feature?
    Copy code
    html
<button hx-post="/whatever"
        hx-on-config-request="event.detail.parameters['foo'] = 'bar'">
  Send Request
</button>
  • m
    basically 
    hx-on
    attributes for all the htmx events
  • l
    Give support library authors a few days' warning to prepare our releases... 🙂 That's a lotta new attributes!
  • m
    rather so
  • m
    I'm not sure this is even a good idea or not
  • m
    does it step on alpine/hyperscript too much? or is it a good 80/20 that would allow folks to not have to bring in another dependency?
  • l
    I'm probably not a good person to answer that; at most, I've found a few plain JS functions handled what I needed them to do in my UIs. My apps tend to be boring use a minimal design.
  • m
    I like it because it feels pretty consistent with standard html attributes
  • r
    Wasn't sure if this was the original proposal, 1cg, but... Imagine using 
    hx-on-*
    to capture ANY event, not just htmx ones 👀 htmx could universally handle 
    hx-on-yourevent
    , the side effect being all htmx events too. Would keep the implementation and extra documentation to a minimum as well.
  • r
    basically classic html 
    on*="..."
    but extended to handle whatever event you want.
  • r
    Contrived case, but these would be equivalent: 
    hx-on-click="..."
    🔁 
    onclick="..."
  • r
    the only reason I don't use 
    onclick="..."
    etc. more often is because custom events are not supported, otherwise they are super convenient (supports async, too!). It'd be very on brand for htmx being an extension of html.
  • r
    sounds like a feature someone may want to use htmx for all by itself 👌
  • r
    I generally agree, that there is a use case for that, but I'm not so sure about the syntax. Specifically, having a separate attribute for each event looks like bloat. I agree with gnat here, htmx should support handling any event, but I'm not sure if current syntax allows to do this efficiently. On the other hand, I didn't try it, so maybe I'm overestimating how slow such implementation could actually be
  • r
    For implementation, i'm simply thinking: if 
    <div hx-on-yourevent="..." />
    exists, setup event listener for 
    yourevent
    on that element using 
    "..."
    . No need to pre-setup every possible event.
  • e
    Isn’t it basically x-on from alpine.js?
  • v
    imo this is exactly what hyperscript is for
  • r
    Yup- the bang for buck is high. An attribute that could remove client side libraries for many projects, by extending a concept already in HTML.
  • c
    I'm looking for a type-safe template cross-platform engine to represent htmx views. While Mustache and Handlebars are cross-platform they provide limited type safety (static analysis when consuming the template and providing the context). On the other-hand, there are many type-safe template engines such as Swirl and Rocker which are type-safe but not cross-platform (we want different platforms to consume those templates).
  • gomponents, view components in pure Go
    e
  • e
    What you’re looking is something jsx-like
  • Type safe HTML sounds a little funny to
    e
    Type safe HTML sounds a little funny to me, because web spec did everything they could to make HTML works even if it’s broken 😀
    c
    • 2
    • 2
  • e
    Anyway if you really want to be on the safe side, use some backend library to generate HTML from ast like gomponents.
  • e
    You can then leverage your language of choice type system to build type safe components.
1...106910701071...1146Latest