Navigation, crews, and party websockets
commit2026-01-14 · schuss
Big day. End to end navigation now works with first mile and last mile walking directions via Mapbox, plus turn by turn aggregation that groups consecutive edges on the same run or lift instead of treating every segment as its own step. Crews, parties, and the websocket broadcast layer landed together, with the PartyKit worker config wired up and the JWT user id mismatch (req.user.userId vs req.user.id) cleaned out of the controllers that were quietly broken because of it. Also fixed route duplication, made the location batch endpoints actually pull userId from the token instead of trusting the client, and added a disclaimer in the UI when lift ride times aren't known. The types file got reformatted to drop semicolons, which I'm choosing not to think about too hard.
9 commits across 1 repo (schuss: 9). 30 files changed. Diff was truncated for summarization.
Related
- ProjectSchuss(getschuss.com)