https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • t
    property/attribute syntax, yes
  • t
    at least it's better than ruby/rails' 
    @prop
  • m
  • m
    alpine is still using kebab attributes
  • t
    no, alpine blows
  • m
    lol, OK
  • m
    well, I don't feel too strongly about it, how do others feel?
  • m
    let me look at the code and see how hard it would be to generalize
  • t
    i mean, it'd be great if it could do some normal 
    <components/>
    , you know 
    <not-retarded>ones</not-retarded>
  • t
    and i'm not even mentioning single file components
  • m
    OK, so not terrible to add delimiter support, but I'm gonna need to hear from more than one random dude on discord
  • t
    you have 20 more random people
  • m
    let's hear it folks
  • g
    This conversation has been very fun to catch up on. But, I'm not sure what the purpose would be. Are you saying that you'd rather we switch from 
    hx-get
    to 
    hx:get
    ? If so, why? What do we gain from that?
  • g
    And honestly, I'm just a random dude on Discord, too. But, text conversations make it hard to decipher people's tone. And @User right now, from your tone, it sort of sounds like you're trolling us.
  • t
    wrong, i have absolutely no tone here
  • t
    my messages are very dry
  • g
    With that said, reusable "components" are awesome, and I agree that if we can help to implement them in HTMX, it would be a win. So, let's focus on the features. What would "components" look like?
  • t
    see riot
  • t
  • t
    *.riot
    specifically
  • g
    Yeah, cool. Thanks 🙂 I'm familiar with web components in general (Angular, unfortunately) and have poked around with Riot.
  • t
    riot can do 
    <this/>
  • t
    your average web components can't
  • g
    I do think it would be cool to be able to pull Javascript state in to HTMX interactions. I was just catching up on the documentation so that I don't embarrass myself 🙂
  • g
    HTMX has 
    hx-include
    that hints at this capability. Perhaps this is something that could be expanded/enhanced?
  • t
    also, i'd use components separately without dragging the whole htmx
  • g
    This came up in one of the examples I commented on, earlier. It was something about two related select statements. I really wished I could do something like this 
    <select hx-get="/sub-options?parentId={this.value}" hx-trigger="change">...</select>
  • g
    @thankful-addition-60522 - yes. Or, being able to use/re-use a static HTML file that didn't depend on the users state, so much. I think that's what my code snippet above is hinting at. Yes?
  • t
    maybe, but i'd use mustache syntax for interpolated vars
1...596061...1146Latest