Scott.Idem/OSIT-AE-API-FastAPI
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(v3-standardization): implement ID Vision for Event models and update docs

Browse Source
This commit is contained in:
Scott Idem
2026-02-05 17:37:52 -05:00
parent 907ff9a2f8
commit 12d725f468
3 changed files with 117 additions and 222 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
documentation/GUIDE__V3_FRONTEND_API.md
View File

@@ -169,8 +169,9 @@ The following endpoints are maintained for backward compatibility but should be
V3 uses a **String-Only ID Vision**. The frontend NEVER handles or stores database integers.
1. **Automatic Mapping:** Internal `id_random` fields are mapped to `id` and `account_id` in JSON responses.
1. **Automatic Mapping:** Internal `id_random` fields are mapped to clean names (e.g., `id`, `event_id`, `account_id`) in JSON responses.
2. **Intelligent Resolution:** You can send random string IDs back to the API in any `*_id` field; the API resolves them to integers before database insertion.
3. **Suffix Compatibility:** The `_random` suffix (e.g., `event_id_random`) is maintained for backward compatibility with V2 clients. Standard V3 frontend integration should prioritize fields without the suffix.
---