jordi fita mas
0b74c7a91c
I use HTTP 422 to signal that a form was submitted with bad data, which i believe is the correct status code: “indicates that the server understands the content type of the request content […], and the syntax of the request content is correct, but it was unable to process the contained instructions.”[0] htmx, however, treats all 4xx status codes as error and, by default, does not swap the target with the response’s content. Until i found out that i could change that behaviour, i worked around this limitation by returning HTTP 200 for htmx requests, but it is a waste of time given that htmx _can_ accept HTTP 422 as a non-error. [0]: https://www.rfc-editor.org/rfc/rfc9110#name-422-unprocessable-content |
||
|---|---|---|
| .. | ||
| fonts | ||
| alpinejs@3.12.0.min.js | ||
| bars.svg | ||
| custom-elements@1.3.0.min.js | ||
| htmx@1.9.2.min.js | ||
| invoice.css | ||
| numerus.css | ||
| numerus.js | ||
| numerus.svg | ||
