No canonical snake_case/camelCase serialization policy
This commit is contained in:
@@ -1,24 +1,3 @@
|
||||
## 24) API response wrapper shape is inconsistent
|
||||
- Where found:
|
||||
- [backend/app/routers/dashboard.py](backend/app/routers/dashboard.py)
|
||||
- [backend/app/routers/jails.py](backend/app/routers/jails.py)
|
||||
- [frontend/src/types](frontend/src/types)
|
||||
- Why this is needed:
|
||||
- Inconsistent payload envelopes increase frontend branching and integration bugs.
|
||||
- Goal:
|
||||
- Define and enforce a consistent response envelope policy.
|
||||
- What to do:
|
||||
- Standardize endpoint response forms.
|
||||
- Align frontend typing and parsing strategy.
|
||||
- Possible traps and issues:
|
||||
- Breaking contract for existing clients.
|
||||
- Docs changes needed:
|
||||
- Add API response style guide.
|
||||
- Doc references:
|
||||
- [Docs/Backend-Development.md](Docs/Backend-Development.md)
|
||||
|
||||
---
|
||||
|
||||
## 25) No canonical snake_case/camelCase serialization policy
|
||||
- Where found:
|
||||
- [backend/app/models/server.py](backend/app/models/server.py)
|
||||
|
||||
Reference in New Issue
Block a user