https://htmx.org logo
Powered by
# htmx-general
  • m
    with a target of the table
  • m
    and then the form targets a div surrounding both the form and the table
  • f
    ohh and have the form's target include both
  • m
    internally that uses a partial that includes the table partial
  • m
    (whatever the django equivalent of partial templates is)
  • m
    Yeah, nest them
  • m
    and use a nice nested URL layout
  • f
    So. many. urls. But that is simplest. Do I have to do anything fancy to initialize htmx/hyperscript on the reloaded form?
  • m
    if it makes you feel better, you can use one URL and look at the 
    HX-Target
    header: https://htmx.org/reference/#request_headers
  • m
    you should not
  • f
    That does make me feel a little better... alright, I might do that to start since even with a 
    refreshTable
    event, I would still need to send the form back
  • m
    yeah, it's more REST-ful and web-ish
  • m
    Copy code
    GET /things -> render table & form
 POST /things -> render table & form
 GET /things/table -> render table only, polled against
  • m
    Copy code
    html
  <div>
    <form hx-post="/things" hx-target="closest div">
       ...
    </form>
    <table hx-get="/things/table" hx-trigger="every 30s">
       ...
    </table>
  </div>
  • f
    Okay, so that's helpful in a few ways (especially 
    closest div
    working for parent, that's great), but I was first trying to do this with the form and then optionally table, so I marked the table 
    hx-oob-swap
    but then when it was just getting polled on it's own it failed to just insert it and it generated a 
    htmx:oobErrorNoTarget
    error. I suppose that you can't just insert html tagged with oob.
  • m
    if you had an id on the table, it should have worked. the 
    oobErrorNoTarget
    error means it can't find the thing to swap
  • m
    but I like that pattern above, less janky more webby
  • f
    Yeah, me too, I'm just restructuring some of the HTML, trying to figure out the best way to segment things and avoid having any overlap between files.
  • f
    Pattern wise, the only thing that isn't obvious would be 
    GET /things -> tender table & form
    since why would /things also return a form. It obviously makes the most sense in this case, just structurally is a bit odd.
  • m
    makes sense from a hypermedia standpoint: you want to return the data and the actions available on that data
  • m
    but it's a mindset shift, for sure
  • m
    😑
  • m
    be the uniform interface you want to see in the world
  • s
    I wrote about my best practices with django and htmx here: https://github.com/guettli/django-htmx-fun Feedback is welcome. I am new to htmx, too. Please tell me if you think something is missing.
  • s
  • m
    answered
  • p
    @User did you have time to look at the hx-action extension pr? https://github.com/bigskysoftware/htmx/pull/493
  • m
    hey tony, I have been thinking about this a lot
  • m
    I am wondering if we should offer this as part of the library itself
  • m
    you mind giving me a bit more time to grind on it?
1...301302303...1146Latest