https://htmx.org logo
Powered by
# htmx-general
  • t
    I don't know how you'd do that, but I guess you could
  • h
    what's your backend - if you want this amount of data to be in sync real time it might make sense to use a websocket/sse
  • f
    If something is off screen it doesn't need to be updated particularly often I suppose
  • f
    Django
  • h
    polling feels like the wrong approach given the number of requests you're making
  • h
    I really really wish Django had ws built in
  • h
    channels aren't terrible but it's a lift to configure
  • f
    Yup. Channels is alright, but that's a whole road of complication
  • f
    This is why the page currently refreshes on every POST (to force a manual refresh)
  • h
    well you could potentially just hx-get poll at the top most element and just use hx-select
  • h
    if your form fields all have id's they should keep state right
  • t
    wait does 
    hx-select
    work for multiple elements?
  • h
    just do the whole page
  • f
    If they have id's, they'll keep state on a full page poll? (well element poll)
  • t
    Can't do the whole page because it would overwrite inputs currently being edited
  • h
    I thought (haven't tested) that if they had an id htmx would merge the state
  • f
    I was looking into saving the contents of each input as session storage but that went down a whole road of messy too.
  • f
    That would be really helpful of htmx...
  • m
    might be worth trying the morphdom extension: https://htmx.org/extensions/morphdom-swap/
  • m
    and polling the whole thing and letting morphdom sort it out
  • h
    is there a checklist in your head for when morphdom makes sense over vanilla?
  • f
    Cool, let me take a look at it
  • f
    Apart from that, any suggestion on how to handle the simultaneous delete issue? (one user deleting then it still appearing for another user who then deletes it). Part of me was thinking it might be better UX wise to just mask the 404 and make it look like the item got deleted (even though it already was). But that might not be the best plan from an error handling perspective
  • m
    i think, from a stateless perspective, if someone asks for a delete and the resource is deleted, a 200 response is appropriate
  • m
    however, I no longer fight over HTTP response codes, I have laid down my guns
  • g
    Hiding the 404 with client-side code is the best way to go imo
  • m

    https://c.tenor.com/uxeFhBi_IVgAAAAd/leaving-sneaking.gif▾

  • t
    On further analysis, a full-page poll with 
    hx-swap-oop="true"
    on all the data table bodies is probably the easiest way to implement this for you
  • t
    Also, is there a way to make a specific request ignore oob swaps?
  • f
    ha yeah, appropriate codes is one of those fights. But that makes sense, especially on an htmx request. if it was a direct API request I'd struggle with not returning a 404 🙂
1...670671672...1146Latest