https://htmx.org logo
Powered by
# htmx-general
  • j
  • m
    ctrl-f "htmx" 0 results 😑
  • j
    ThoughtWorks will catch up in a few years. That they even considered Hotwire and non-SPA is impressive.
  • m
    🙂
  • m
    If ThoughtWorks ever mentions htmx I'll lose my mind
  • b
  • b
    Soon to be a podcast episode here: https://changelog.com/jsparty
  • t
    I don't think we have enough traffic to justify any of that at the moment. We have a bunch of self-explanatory channels for different stacks, and anything that isn't specific to any stack currently fits into the general channels without any issues, at least from my perspective. As for FAQs, I have yet to answer the same question twice here, I think. But if you can identify frequently asked questions, I'd be all for a pinned message and/or adding that to the htmx website
  • b
    This brings up the previous discussion as to whether Discord is the right place for support or whether GitHub Discussions (or something else) would be better.
  • r
    both provide quite a lot of value imo: discord is powerful as a community growth platform and spontaneous discussions. A lot of value comes from the brainstorming here. github discussions are for long term discussions that need permanence, google-ability. It's more akin to stack overflow.
  • r
    discord also keeps a lot of fluff out of the github issue tracker.
  • f
    If we could have an easy way to pinpoint recurrent subjects/questions/patterns it would be nice. But I can't think about a simple way to do that... We could have someone who will be pleased to commit itself to this task, then if someone has day a sensation of déjà-vu because of a message, we call it with a '@' and then make a thread in GitHub discussion about the subject.
  • s
    I want to implement the following pattern: If a 
    hx-post
    fails, the server returns some HTML and it is displayed using 
    hx-target
    on the client. However, if the request succeeds, I want to send a 
    303
    response from the server and redirect to completely different server side generated page. What's the best way to solve this?
  • s
    Sending a 
    303
    currently just renders the HTML of the page to be redirected to where 
    hx-target
    points to.
  • s
    Adding the 
    HX-Redirect
    header did the trick but I had to use a 
    200
    response. Is there a specific reason not follow the 
    303
    directly instead of having a new header?
  • f
    Building on this question I have another question (maybe more important) : Is there a solution to configure htmx manually in order to say: if 303, do a HX-Redirect to the new location. It would be so cool to have a simple API to tweak the htmx behavior for specific use cases...
  • s
    I was thinking about this as well. This would bring us closer to "bare metal HTTP".
  • w
    I think the main problem with that solution would be that the underlying ajax request (aka fetch) would have to not follow redirects at all, which I guess would break other things
  • t
    Should be easy enough to make an extension for that
  • t
    he said, having no idea if that was true or not
  • m
    assuming that the client side sees the response, you can modify response behavior like so: https://htmx.org/docs/#modifying_swapping_behavior_with_events
  • m
    however for many redirects, htmx never sees the initial redirect response, it is entirely handled by the browser and never hits our code
  • f
    Dude, you really though about everything beforehand, didn't you?
  • f
    One of the most impressive thing about htrmx IMHO, is that when anyone ask a question here, @1cg has always an answer: - use 
    hx-foo
    - try the 
    hx-bar
    option /modifier - you can do it with the 
    HX-Baz
    header - just rethink the workflow of your client/server interactions...
  • f
    It's like htmx has always a solution for any use case. This is huge.
  • a
    I am trying to understand why I am not seeing checkbox values being included using 
    hx-include
    . My checkboxes look like:
    Copy code
    <input type="checkbox" name="expire" value="<%= deal.id %>">
    and I submit them with this button:
    Copy code
    <button id="bulk-expire-btn"
            hx-post="/expireDeals"
            hx-include="[name='expire']"
          >
    and I am testing on the backend (express) like this:
    Copy code
    app.post('/expireDeals', function(req, res) {
  console.log(req.params, req.query)
  res.send('a test')
})
    But the only output I see in my express server log is: 
    {} {}
    . I am expecting to see a list of ids because I have checked a handful of the checkboxes before submitting.
  • t
    Do all of your checkboxes have the same name, 
    expire
    ?
  • a
    Yes.
  • t
    Try 
    expire[]
  • g
    what does 
    req.body
    log?
1...657658659...1146Latest