https://htmx.org logo
Powered by
# htmx-general
  • m
    lmao
  • m
    \> yo no cap u don't even need that for web dev fr \> hypmermedia straight bussin' \> mf deadass simple fr
  • r
    the comradery in this chat is humbling
  • r
    most of us will probably never meet each other in meatspace
  • r
    but there's no other space with so many like-minded devs
  • r
    resume driven development does not exist here
  • r
    or rather, drastically less than every other community.
  • r
    totally anti-hype
  • a
    back again... 😬 is it possible to have one button trigger multiple get request calls for different targets? Or is it possible to bind to multiple templates with a single call?
  • h
    multiple templates you can do with oob swaps
  • h
  • a
    Hmmm 🤔 unfortunately this isn't very clear on implementation
  • a
    I also feel like generally there's a lack of clear and concise examples 😬
  • m
  • m
    🙂 I really enjoy chatting with everyone here
  • t
    I come back to this topic every so often and I do think we could use a way to define multiple hx-gets instead of relying on oob swaps. But I can't think of a clean syntax for them.
  • m
    keep wrenching on it
  • m
    I'm open to ideas for sure
  • t
    Multiple 
    hx-get
    properties would just override eachother right?
  • t
    It might be an abuse of html tags, but something like
    Copy code
    html
<button hx-multiget>
<x-htmx hx-get="/foo" hx-target="#foo">
<x-htmx hx-get="/bar" hx-target="#bar">
Click here to update things
</button>
  • t
    Or just 
    hx-get="/foo,/bar" hx-target="#foo,#bar"
    and make that throw all kinds of errors if you don't have an equal number of gets and targets
  • m
  • m
    🤔
  • c
    thanks for sharing your wisdoms. `` JavaScript (natural ether of complexity demon!)`` 🔖
  • b
    On the topic of multiple hx-gets, I highly suggest implementing the others with some hyperscript to see if it feels better than oob stuff. The question "hey can we simplify this pattern I found useful" is a much easier negotiation than "hey can we implement this theory of mine"
  • b
    Another idea on the same topic is to enhance your API w queries for extra oob stuff, like 
    my.api/my/fragment?withOob=otherFragment:#otherTarget
  • b
    Just thoughts, not trying to squash any conversations!
  • m
    Or, push that work to the backend so that it is a single GET?
  • b
    That's my proposal starting with "Another idea": you give the flexibility to the frontend to request more oob stuff in a single request. That "withOob" query could be available on every single API call, not coupled to any individual call. Therefore you get the same expressive power to get what you want from the frontend as you would with multiple hx-gets
  • t
    That's what we currently do with oob swaps. With multiple hx-gets, we could simplify the backend while also being explicit in a standardized way on the frontend.
1...710711712...1146Latest