https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • a
    like if I have form A trigger on change, and that trigger targets form B. But form B also has an hx-trigger=Change, should that trigger?
  • r
    you can send empty form in the response as oob swap. But honestly, I would use JS (or hyperscript).
    Copy code
    on htmx:afterRequest[detail.successful] reset() me
  • r
    Probably shouldn't > The change event is fired for , , and elements when an alteration to the element's value is committed by the user. Unlike the input event, the change event is not necessarily fired for each alteration to an element's value. > https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/change_event
  • a
    That's what I thought ok
  • m
  • m
  • r
    I'd love to hear grug describe the best way to do form validation with hypermedia
  • r
    (that's a common response I get when talking about HTMX - form validation requires a trip to the server)
  • m
    Validation should probably happen (or is already happening) on the server anyway… In my experience, having access to the populated data model / submission in the template/view and outputting submitted values and validation issues (as you would with a traditional MPA) works pretty well!
  • p
    Client form validation has given me nothing but hell over the years. Seen it done, and redone, and redone for the same application
  • p
    Most of the issue is the insistence on the client-code handling a lot of scenarios, when it really needs to be "API first". That catch phrase that everyone says but never actually likes doing
  • r
    Validation has to happen on the server anyway. HTMX can make it nice enough that it feels client side.
  • r
    although we always need docs of good patterns on htmx.org, for sure.
  • r
    we're all so early to the party I think a lot of the best, shortest, language agnostic patterns using the building blocks htmx / hyperscript gives us are still yet to be documented.
  • m
  • m
    it's a shitposting day I guess
  • m
  • h
    I just spent two days(12 hours daily), writing damn comment display and pagination(json from backend) in JQuery. I'm really ready for something like HTMX.
  • m
    Copy code
    html
  <a hx-get="/post/${post.id}/comments?page=${page + 1}" ...>
     Load More
  </a>
  • h
    That's more like it.
  • l
    The easiest htmx way to do this would be to always return the list and an empty form, assuming you're persisting the list on the server. When you first pull, the page contains "the list" (nothing, because it's empty) and a form. When you submit the form, you persist item one, and return "the list" (now with 1 item) and the same empty form. Repeat to your heart's content. You can come back to your list, and it's still there; you can add more later. (If you're not persisting the list on the server, then the above doesn't apply; but, if you're persisting it in the browser, you wouldn't need to "submit" it anywhere.)
  • h
    So I've heard it's best practice to use with another library like Alpine?
  • m
    vanillajs, alpine or hyperscript seem to be the most popular for front end scripting needs
  • a
    Copy code
    html
hx-include="#previous select"
  • a
    @mysterious-toddler-20573 is this supposed to work? Am I doing it wrong?
  • m
    previous select
  • m
    # is the start of an id reference
  • h
    Are there shortcommings of htmx where it's needed?
  • m
    if you want pure client side interactions, such as toggling a class on a div or whatever, and a server round trip isn't ideal
  • a
    how do I add a custom parameter without taking away the default parameter?
1...733734735...1146Latest