Skip to content

Add persisted ride history feature#290

Draft
davixcky wants to merge 2 commits intocursor/dev-env-setup-e51bfrom
cursor/ride-history-feature-f02b
Draft

Add persisted ride history feature#290
davixcky wants to merge 2 commits intocursor/dev-env-setup-e51bfrom
cursor/ride-history-feature-f02b

Conversation

@davixcky
Copy link
Copy Markdown
Contributor

@davixcky davixcky commented Apr 9, 2026

Summary

  • add persisted ride history storage in the location service (ride_history table) with APIs to create entries, list rides per session, and update driver plate per request
  • update frontend backend handlers to store ride requests at dispatch time, expose a /ride-history response with total count + list, and backfill driver plate from driver dispatch notifications
  • add home page UI to show ride history as a list view with pickup, dropoff, request time, driver plate, and total requested rides
  • add a Signadot smart test for the new ride-history endpoint behavior in the hotrod-devmesh namespace path

Validation

  • focused Go tests for changed services pass
  • local end-to-end run validates /dispatch persists ride history and /ride-history returns expected fields/count
  • Signadot smart test run fiiwfv46l4hs (existing dispatch test) completed in sandbox driver-plates
  • Signadot smart test run fiixg1nmmznk (new ride-history test) executed against frontend.hotrod-devmesh.svc and reports expected 404 check failures on baseline/target, confirming endpoint expectation gap in deployed environment

Walkthrough artifacts

ride_history_feature_demo.mp4
Ride history initial state
Ride history final state

To show artifacts inline, enable in settings.

Open in Web Open in Cursor 

cursoragent and others added 2 commits April 9, 2026 01:29
Co-authored-by: David Orozco <davixcky@users.noreply.github.com>
Co-authored-by: David Orozco <davixcky@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants