bigskysoftware / bigskysoftware/htmx
Support `hx-status:*="#error"`
- Dominant language
- JavaScript
- Stars
- 49.4k
- Forks
- 1.7k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 30
Description
Hi!
Thank you for the excellent HTMX v4 library!
Are there plans to support `hx-status:*="#error"` to catch all not explicitly handled errors? Currently 4xx and 5xx errors have to be handled separately, even if they have the same target:
* `hx-status:422="#form" hx-status:4xx="#error" hx-status:5xx="#error"`. It is much more convenient to substitute this with just
* `hx-status:422="#form" hx-status:*="#error"`.
Thank you!
Contributor guide
Research direction
No file or test is identified in the issue. Start by tracing the existing hx-status response handling and its separate 4xx/5xx matching, then verify that a wildcard handles statuses not explicitly listed while the specific 422 target still takes precedence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100