Files
devplacepy/devplacepy
typosaurus ff49c8342a feat(nadia): Update API documentation for profile endpoints with new response fields
Outcome: done
Changed: `devplacepy/docs_api/groups/profiles.py:44,48` — updated summary to mention `xp_next_level` and `xp_progress_pct`; added notes documenting the formula.
Verified by: `python3 -m py_compile devplacepy/docs_api/groups/profiles.py` — pass.
Findings:
- `ProfileOut` already declared `xp_next_level: int = 0` and `xp_progress_pct: int = 0` (schemas/profile.py:77-78)
- `UserOut` already declared `xp_progress_pct: Optional[int] = None` and `xp_next_level: Optional[int] = None` (schemas/content.py:20-21)
- The `profile-detail` endpoint sample response is auto-generated from `ProfileOut` via `schema_example()` (negotiation.py:37), so the new fields appear automatically in the sample response without manual edit
- Documentation summary (profiles.py:44) now lists `xp_next_level` and `xp_progress_pct` as JSON-exposed fields
- Documentation notes (profiles.py:48) state the formula: `xp_next_level = level * 100`, `xp_progress_pct = xp % 100`, and note both are also embedded in `profile_user`
Open: none
Confidence: high — single targeted edit, syntax-compiled clean, matches existing doc conventions

Typosaurus-Run: a6697d32c4ea49b4a9767bd5a8c1119f
Typosaurus-Node: a445e4e802ac4d95b69169b1a4e34185
Typosaurus-Agent: @nadia
Refs: #112
2026-07-26 23:28:32 +00:00
..
2026-07-09 02:52:54 +02:00
2026-07-26 16:46:41 +02:00
2026-07-26 16:46:41 +02:00
2026-07-26 16:46:41 +02:00
2026-07-26 16:46:41 +02:00
2026-07-09 02:52:54 +02:00
2026-07-19 18:57:43 +02:00
2026-07-19 18:57:43 +02:00
2026-07-19 18:57:43 +02:00
2026-07-26 16:46:41 +02:00
2026-07-19 22:55:47 +00:00
2026-07-26 16:46:41 +02:00
2026-07-26 16:46:41 +02:00
2026-07-09 02:52:54 +02:00
2026-07-26 16:46:41 +02:00