- ID
- aba7d856-f023-490a-ba45-70aff13c345d
BE-6508 Client migration doc follow on POST /api/reschedule_order/
- source :: https://hungryroot.atlassian.net/browse/BE-6508
- tags :: Hungryroot API Project
- epic :: EP-411 Eng Parking Lot
- sprint :: HR BE Sprint 102 HR BE Sprint 103
- status :: Status - Complete
DONE Investigate V2 to find a matching endpoint for api/reschedule_order
- ID
- d0b515d9-3990-47a8-a18f-bfe6471a6a43
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" POST /api/reschedule_order/ 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: