## 27) Error response body shape is inconsistent
This commit is contained in:
@@ -1,24 +1,3 @@
|
||||
|
||||
## 26) Pagination contract is not standardized across endpoints
|
||||
- Where found:
|
||||
- [backend/app/routers/dashboard.py](backend/app/routers/dashboard.py)
|
||||
- [backend/app/routers/history.py](backend/app/routers/history.py)
|
||||
- [backend/app/routers/blocklist.py](backend/app/routers/blocklist.py)
|
||||
- Why this is needed:
|
||||
- Different pagination patterns increase frontend complexity.
|
||||
- Goal:
|
||||
- Use one shared paginated response model.
|
||||
- What to do:
|
||||
- Introduce common pagination schema and query parameter policy.
|
||||
- Possible traps and issues:
|
||||
- Existing endpoint consumers may require transition period.
|
||||
- Docs changes needed:
|
||||
- Add pagination API spec.
|
||||
- Doc references:
|
||||
- [Docs/Backend-Development.md](Docs/Backend-Development.md)
|
||||
|
||||
---
|
||||
|
||||
## 27) Error response body shape is inconsistent
|
||||
- Where found:
|
||||
- [backend/app/main.py](backend/app/main.py)
|
||||
|
||||
Reference in New Issue
Block a user