https://htmx.org logo
Powered by
# htmx-general
  • n
    I wonder if it would be a good idea to keep track of in-flight requests and a setting to prevent multiple in-flight request to the same URL
  • n
    In ember.js land we have ember-concurrency that let's us specify how to handle concurrency https://ember-concurrency.com/docs/task-concurrency what I would like to specify is the "drop" behaviour
  • m
    htmx has an event queuing mechanism
  • m
    the easiest thing it to allow multiple elements share a queue
  • h
    Is there a consideration w/ creating an event that results in an ajax request from inside an htmx event?
  • h
    I am firing off an hx-get, then in an after settle I click a button
  • m
    i just found out the event queueing behavior is undocumented 😑
  • h
    the button click will trigger an ajax event
  • h
    I am seeing in that situation two requests go out, one that's an ajax request and one that's a real document refresh
  • h
    bleh never mind
  • h
    I can repeat the behavior on the console
  • h
    it's unrelated 💢 but it breaks only when using a programatic event not from a real click
  • m
    😑
  • m
    actually it is documented, but hidden here: https://htmx.org/attributes/hx-trigger/
  • m
    it's the 
    queue:
    option
  • m
    what I'd like to allow is for an element to share a queue with other elements
  • m
    so in your case both buttons would share a single queue
  • m
    I've never used the queue option, but I recently faced a somewhat related issue. I have a form that submits a post request on 
    submit
    . Within that form I had some inputs that trigger a request to update the form (for instant validation) on 
    blur
    (i think that's what it was, I changed it to keyup with a delay and may end up removing altogether). If you type something on the input, then scroll down to click the submit button, then it triggers both events almost at the same time which leads to swap errors.
  • m
    🤔
  • m
    In that case it would be great if the blur event request could be cancelled/aborted. Not sure if that's even possible.
  • b
    Ember Concurrency is really nice. Uses some generator magic to make things cancellable etc. The docs site has some nice interactive examples of what it offers: http://ember-concurrency.com/docs/introduction/ Just FYI
  • b
    Doh. @User already linked you. One of these days I'll read the whole message.
  • m
    I will look at this
  • m
    it's an area I'd like to improve, but I want to keep things declarative if possible
  • m
    I think a declarative sync mechanism might be enough:
    Copy code
    html
<form hx-post="...">
     ...
     <input hx-get="..." hx-sync="closest form : drop">
     ...
</form>
    (thinking out loud here)
  • b
    The behaviours are nice - set a task to repeat, drop if one is running, drop the running one, queue them up, run in parallel. Things like deboucing are easy to implement.
  • m
    i'll read over it and think
  • m
    maybe something for hyperscript too
  • b
    It's useful for when you don't have transparent asynchonousity and all that.
  • b
    But I'll leave you to ponder. For no reason whatsoever.
1...524525526...1146Latest