Promote dev → uat: GRO-2159 drag-to-reorder + re-optimize #64
Reference in New Issue
Block a user
Delete Branch "promote/GRO-2159-dev-to-uat"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Promote dev → uat: GRO-2159 drag-to-reorder + re-optimize
Promotes the GRO-2159 route-planner drag-to-reorder feature to
uat.Built on
uat(which already has GRO-2158's planner via #61) by cherry-picking the GRO-2159 squash commit only — this isolates the feature and deliberately does not drag along dev's in-flight portal fixes (#51/#53/#54/#55/#57) that have not yet been promoted to uat.Scope (vs uat)
src/pages/Routes.tsx— @dnd-kit sortable stop list, sensors, optimistic reorder + rollback, re-optimize buttonsrc/__tests__/Routes.test.tsx— drag handle / conflict / no-pre-hint / reorder-mock testspackage.json+pnpm-lock.yaml—@dnd-kit/core,@dnd-kit/sortable,@dnd-kit/utilitiesUAT_PLAYBOOK.md— §5.29 (7 drag-to-reorder & re-optimize test cases)Verification (on dev pre-merge)
typecheck ✅ · lint ✅ · 179 tests ✅ · build ✅ · CI green on #63
QA: please review against UAT_PLAYBOOK.md §5.29. Source: GRO-2159.
QA review complete — LGTM.
Review summary
CI: Lint & Typecheck ✅ · Test (179 tests) ✅ · Build & Push Docker ✅ · No conflicts
Code (Routes.tsx):
manuallyReorderedflag correctly gates the re-optimize hint/banner; cleared on optimize or fresh fetchencodeURIComponent(routeId)on PATCH URL — securedisabled={reordering}prevents overlapping concurrent reorder requestsTests (Routes.test.tsx):
UAT_PLAYBOOK.md:
Approved for uat merge.