- ID
- c59a475f-00dc-4dc7-ace6-a109592c9026
BE-6504 Client migration doc followup GET /api/get_tag_group/
- source :: https://hungryroot.atlassian.net/browse/BE-6504
- tags :: Hungryroot API Project
- epic :: EP-411 Eng Parking Lot
- sprint :: HR BE Sprint 105
- status :: Status - Complete
Tasks
DONE Review current stats and update Confluence doc for /api/get_tag_group
- ID
- 40bca748-1c27-67f0-a987-a22dafd5be80
Description
Over time, we've been creating DRF powered "v2" endpoints (routes are prefixed
with /api/v2/) that allow for out-of-the box API contract discovery and
documentation through the drf-spectacular swagger interface. We want to migrate
away from v1 endpoints (v1 routes don't have a version prefix, just /api/) defined
in app/urls/apiv1.py
Analyze whether the "v1" GET /api/get_tag_group/ endpoint has a "v2" DRF
equivalent under the app/rest/ directory. If it does, explain differences in the
API contracts: both responses and supported request body fields and/or query
params between the two.
Acceptance criteria:
[ ] Update the v1 -> v2 migration Confluence doc for the specified section: