https://htmx.org logo
Powered by
# htmx-general
  • m
    Yes, I am using this approach right now. The only drawback is when you have a state you want to maintain that is also within the html you are swapping.
  • m
    It's not a big deal that cannot be worked around though
  • s
    if you return a 4xx or 5xx htmx doesn't swap but i would assume tiggers still apply.
  • s
    though technically i haven't tried it yet, it is my plan for form validation though so I hope it works.
  • g
    Yes, looking at it again, I think that's what the 
    hx-swap="beforeend"
    is doing, essentially appending an empty result to the end of the body. Maybe that's a case for an 
    hx-swap="none"
    option.
  • s
    true but i can definitely see a need to let the server control if the swap should occur
  • g
    You're right. There are many other situations where the server should control that. For this modal example, it's always the same.
  • s
    but tbh id generally return an error code anyway in most of those cases.
  • g
    šŸ™‚
  • g
    Yes, so would I. client side validation, then server side validation after. Maybe it was you, but someone on here mentioned that they just put the "pretty" error messages in the client-side validation. If server-side validation fails, that (almost always) means that the user is trying to circumvent something, so they just barf and don't say why. I loved this idea, and will be trying that out whn I get there...
  • s
    also have a usecase i am not sure if its possible, I want to append something to every query string when htmx makes a query
  • s
    Yes this is generally the way i recommend it too I have seen team memebrs spend ages on 'pretty' error messages for states that are only reachable if the code is flawed or people mess with the js validation.
  • s
    waste of time.
  • s
    However, sometimes the server needs to validate 'business logic' such as customer deduplication based on business id or something, in this case you do need a 'pretty' error.
  • s
    tbh for client side validation you should also use the browser validation, its better than anything home cooked.
  • m
    Copy code
    on closeModal(event) 
    add .closing to #modal 

    if (not (no event.detail.nextPage))
        set window.location to event.detail.nextPage
    end

    wait for animationend
    remove #modal
end
    not
    Copy code
    on closeModal 
    add .closing to #modal 
    set the location of the window to 
          the nextPage of the event's detail
        unless no nextPage of the event's detail
    settle
    remove #modal
end
    šŸ˜‘
  • m
    šŸ™‚
  • m
    let's golf
  • g
    Yeah, about that..
  • m
    Copy code
    on closeModal(nextPage)
    add .closing to #modal 
    set the location of the window to 
          the nextPage unless no nextPage
    settle
    remove #modal
end
  • m
    should work
  • m
    it doesn't
  • m
    but it should
  • m
    šŸ™‚
  • g
    Copy code
    on closeModal(nextPage) tell #modal
    add .closing 
    set the location of the window to the nextPage
        unless no nextPage
    settle
    remove
  • g
    I tried using 
    settle
    but there's a funny flash of the original modal at the end of the animation. I think it's because of the "wait a tick" logic included in 
    settle
    . I could probably figure out how to update my CSS to accommodate this, but I haven't yet. So 
    wait for animationend
    is still in there for now.
  • g
    I love the 
    unless
    statement. Is that already in /dev?
  • g
    it's good to see that i'm not the only one who brings up hyperscript in the general channel
  • g
    And yes, this could probably be a behavior. As always, I'm using hyperscript "OG Edition" from last week.
  • g
    Oops. I wasn't looking where I was.
1...205206207...1146Latest