https://htmx.org logo
Powered by
# htmx-general
  • m
    w/ empty content
  • m
    Some tempting codes in there
  • g
    empty content, or a message about the deletion
  • g
    Copy code
    HTTP/2.0 200 OK
Content-Type: text/html

<li class="info" _="init wait 2s then remove">
  Item deleted.
</li>
  • m
    Copy code
    410 Gone
  418 I'm a teapot
  • m
    but they are 400s
  • m
    tryna not break the web
  • g
    those are for GETs nope
  • m
    yep, that's the right thing mr aksimsek
  • m
    u r right, hyperscript should be a CERN standard
  • g
    or you can maybe 410 if someone tries to delete sth that was already deleted
  • g
    as I said, 200 is the right thing to return when the expected thing happens
  • g
    which is deletion
  • m
    The year is 2040, CERN declares code on demand a required constraint of rest and recommends hyperscript as the implementation. The small area of land it controls around it rejoices, while the barbarian outlands gnash their teeth.
  • m
    yep
  • m
    agreed, you've talked me off the ledge
  • s
    status codes are an intersting concept, but there is a two pronged problem of them both being outdated for mordern use and newer developers not actually reading the standards but just mashing things together, so they are effectively never respected anywhere.
  • s
    same thing with people only using for everything or never touching anything except GET or POST requests, everything gets reduced the lowest common working set... and don't even get me started on all the decades of great DB features that are reimplemented in the application layer or ignored because everyone is using the lowest common denominator ORM that happens to be vogue this month.
  • g
    Don't forget the horse archers. Walled fortresses always fall to the horse archers -- preferably ones who respect HTTP status code orthodoxy.
  • s
    speaking of which I had an issue with htmx forms not being able to properly close elements.. so I resturn a 'dialog-close' custom header and hook into the htmx request event and check if the header is in the request to see if i should close the
  • s
    Somehow I feel that I am part of the problem which I complain about 😮
  • g
    No, that seems right. I do the same thing, and it works beautifully. Sometimes I need to update the content below the dialog, so I use an OOB-swap along with the "close dialog" event.
  • p
    I have always used 204 as a response code for a delete, based on https://restfulapi.net/http-methods/#delete > A successful response of DELETE requests SHOULD be HTTP response code 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has been queued, or 204 (No Content) if the action has been performed but the response does not include an entity.
  • p
  • m
    Unfortunately, that is in conflict w/ what MDN has to say on the topic: > This might be used, for example, when implementing "save and continue editing" functionality for a wiki site.
  • m
    Kind of a mess, ngl
  • g
    attempt to reconcile: an empty response is an entity, an instruction to show an empty screen, which communicates to the user that the resource is gone, and therefore transmits some message
  • m
  • m
    🤔
  • g
    It's also in conflict with how the standard says it should be handled... Seems wrong to keep showing a resource that doesn't exist anymore
1...356357358...1146Latest