Skip to content

feat: modify /plan-journey so it returns bus polylines, /getAllRoutes & /getAllRideRoutes to return processed data - #47

Draft
jumpy-cat wants to merge 10 commits into
http-api-docsfrom
nav/plan-journey-bus-polylines
Draft

feat: modify /plan-journey so it returns bus polylines, /getAllRoutes & /getAllRideRoutes to return processed data#47
jumpy-cat wants to merge 10 commits into
http-api-docsfrom
nav/plan-journey-bus-polylines

Conversation

@jumpy-cat

@jumpy-cat jumpy-cat commented Jul 25, 2026

Copy link
Copy Markdown
Member

Description

Move the majority of bus route line processing into the backend so that more information in available during journey planning. (WIP) Modify plan journey so that its bus legs contain polyline info. (WIP) refactor all changed routes to use documented.

Type of Change

  • New feature (feat)
  • Bug fix (fix)
  • Refactor / code improvement
  • Dependency / build update
  • Documentation
  • Other (explain)

Related Issues

Backend Side of mbusdev/bluebus-flutter#98

Changes Made

  • Flutter: n/a
  • Backend (TypeScript):
    • the responses from bustime servers /getpatterns are now checked against zod schemas before being processed into BusRouteLines similar to those used in the frontend (but missing a few fields)
    • existing usages of routes / ride routes refactored to use processed bus route lines
  • Firebase / Shared: n/a

Testing Done

Flutter:

  • Tested on:
    • iOS Simulator
    • Android Emulator
    • Physical device

Screenshots / Demo (if UI or notification change)

Checklist

  • Commit messages follow Conventional Commits
  • PR title follows [type](scope): short description
  • PR target branch is not main and is our current working update branch (e.g. maizebus2.1)
  • No print() / debugPrint() / console.log() left in production code
  • Secrets / keys not committed

@jumpy-cat jumpy-cat changed the title feat: modify /plan-journey so it returns bus polylines, uses documented feat: modify /plan-journey so it returns bus polylines, /getAllRoutes & /getAllRideRoutes to return processed data Jul 25, 2026
@jumpy-cat
jumpy-cat force-pushed the nav/plan-journey-bus-polylines branch 2 times, most recently from 032b194 to e5f4055 Compare July 25, 2026 21:44
@jumpy-cat jumpy-cat changed the title feat: modify /plan-journey so it returns bus polylines, /getAllRoutes & /getAllRideRoutes to return processed data feat: modify /getAllRoutes & /getAllRideRoutes to return processed data Jul 26, 2026
@jumpy-cat jumpy-cat changed the title feat: modify /getAllRoutes & /getAllRideRoutes to return processed data feat: modify /plan-journey so it returns bus polylines, /getAllRoutes & /getAllRideRoutes to return processed data Jul 26, 2026
@jumpy-cat
jumpy-cat changed the base branch from dev to http-api-docs August 1, 2026 22:45
@jumpy-cat
jumpy-cat force-pushed the nav/plan-journey-bus-polylines branch from 209f9dc to 1f94be3 Compare August 2, 2026 02:01
@jumpy-cat
jumpy-cat force-pushed the nav/plan-journey-bus-polylines branch 2 times, most recently from 7da68ce to 213fb48 Compare August 2, 2026 19:50
@jumpy-cat
jumpy-cat force-pushed the nav/plan-journey-bus-polylines branch from 213fb48 to 1e2959d Compare August 2, 2026 19:55
jumpy-cat and others added 10 commits August 2, 2026 13:09
Replace the any returned by processJourneys with an actual type that models the two variant nature of the processed legs. Did a similar thing with the journey leg type in `McRaptorAlgorithm.ts`. Both changes should have no semantic difference but behavior and performance should ideally both be checked.
Logic was ported from the frontend, which shall be changed to rely on
the result from the backend.
Both the indexing issue that happened towards the beginning of summer
and the typo that happened while I was porting the logic.
@jumpy-cat
jumpy-cat force-pushed the nav/plan-journey-bus-polylines branch from 1e2959d to 980fb37 Compare August 2, 2026 20:09
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.

1 participant