Project

General

Profile

Edit Copy Actions
Copy link

Bug #10184

open

CREATE RIDE — DONE & WORKING (Stopovers & pricing)

Added by Thirupathirao Uppu about 10 hours ago. Updated about 10 hours ago.

Status:
New
Priority:
Normal
Assignee:
Thirupathirao Uppu
Start date:
08/03/2026
Due date:
08/30/2026 (Due in 27 days)
% Done:

30%

Estimated time:
32:00 h
Spent time:
8:00 h
Tested Date:
08/03/2026
Raised by Tester:
Quote

Description

CREATE RIDE — DONE & WORKING (CHAT TASK LIST)

Stopovers & pricing

  • Google road distance for corridor + each stop (not haversine-only)
  • Fare = remaining km stop -> destination x ₹2.5 (min ₹20)
  • Full-trip / destination seat price separate from stop prices
  • Space near-twin cities (~25–55 km); prefer higher-earning stop
  • Block selecting a stop too close to another (alert + greyed UI)
  • Custom stops also use remaining-to-dest Google km
  • Payload sends distanceKm + remainingToDestKm to backend

Create Ride UI (3 steps)

  • Step 1 — Route & stops: map, From/To Edit, city chips, itinerary with ₹/seat per stop + destination price, tip banner, CTA "Set Ride Details"
  • Step 2 — Ride details: date chips, time chips, seats, destination price + booking gauge, earnings, CTA "Review Ride Offer"
  • Step 3 — Review & Publish: route timeline, ride details, vehicle pick, earnings, policy, green "Publish Ride Offer"

Wiring

  • RouteDetailsStep + DateTimeStep + ReviewPublishStep wired in CreateRide.screen
  • Auto-suggest trip price from Google corridor km
  • Auto-select approved vehicle on Review when none chosen
  • Sync selected stops with Google journey legs when multiple stops

Files touched

  • stopoverSuggestions.ts
  • routes.service.ts
  • RouteDetailsStep.tsx
  • DateTimeStep.tsx
  • ReviewPublishStep.tsx (new)
  • CreateRide.screen.tsx

Quick smoke test

1. Create Ride > long route (e.g. Hyderabad <> Vijayawada)
2. Confirm spaced chips (no near twins both selectable)
3. Earlier stop ₹ > later stop ₹
4. Set date/time/seats -> Review -> Publish

Add

Subtasks

Add

Related issues

QuoteActions
Copy link
 #1

Updated by Thirupathirao Uppu about 10 hours ago

  • % Done changed from 0 to 30

CREATE RIDE — DONE & WORKING (CHAT TASK LIST)

Stopovers & pricing

  • Google road distance for corridor + each stop (not haversine-only)
  • Fare = remaining km stop -> destination x ₹2.5 (min ₹20)
  • Full-trip / destination seat price separate from stop prices
  • Space near-twin cities (~25–55 km); prefer higher-earning stop
  • Block selecting a stop too close to another (alert + greyed UI)
  • Custom stops also use remaining-to-dest Google km
  • Payload sends distanceKm + remainingToDestKm to backend

Create Ride UI (3 steps)

  • Step 1 — Route & stops: map, From/To Edit, city chips, itinerary with ₹/seat per stop + destination price, tip banner, CTA "Set Ride Details"
  • Step 2 — Ride details: date chips, time chips, seats, destination price + booking gauge, earnings, CTA "Review Ride Offer"
  • Step 3 — Review & Publish: route timeline, ride details, vehicle pick, earnings, policy, green "Publish Ride Offer"

Wiring

  • RouteDetailsStep + DateTimeStep + ReviewPublishStep wired in CreateRide.screen
  • Auto-suggest trip price from Google corridor km
  • Auto-select approved vehicle on Review when none chosen
  • Sync selected stops with Google journey legs when multiple stops

Files touched

  • stopoverSuggestions.ts
  • routes.service.ts
  • RouteDetailsStep.tsx
  • DateTimeStep.tsx
  • ReviewPublishStep.tsx (new)
  • CreateRide.screen.tsx

Quick smoke test

1. Create Ride > long route (e.g. Hyderabad <> Vijayawada)
2. Confirm spaced chips (no near twins both selectable)
3. Earlier stop ₹ > later stop ₹
4. Set date/time/seats -> Review -> Publish

Edit Copy Actions
Copy link

Also available in: Atom PDF