Status app endpoints should use etags
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: status
performance 🚀
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Right now they do not user that. Which leads to a lot of extra parsing on the client side as the status codes don't often change.
Should probably not be to hard and a backport would make sense I think.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Status app endpoints and inspecting how their responses are generated and consumed. Confirm the current status response behavior, then verify that unchanged responses can use ETags to avoid unnecessary client-side parsing and that the endpoint behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100