[grantlh1122]

Description

Originally the service for getting Ride predictions would estimate the unix time based on the predicted minutes until arrival field. This changes the function to use the unix timestamp from the Ride API instead.

Type of Change

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

Changed Files

• graphBuilder.ts
  • Changed to use the Ride API estimation when processing Ride predictions.

Related Issues

Subissue of bus notifications tracking issue #33

Does your code rely on another PR

N/A

Testing Done

Flutter:

• Tested on:
  • iOS Simulator
  • Android Emulator
  • Physical device
    Vitest:
• existing test(s) with coverage: 'should get unix timestamp from ride bus api'
• new tests added: (describe)

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, dev)
• No print() / debugPrint() / console.log() left in production code
• Secrets / keys not committed

[jumpy-cat]

Code changes look good. Just one small note: the existing test with coverage is actually should have cached preds in a good state. That test had the ride fields commented out for some reason so I've pushed a commit that uncomments them.