fix: return HTTP 404 for unknown agency ID in stop-ids-for-agency#975
Conversation
|
Warning Review limit reached
More reviews will be available in 56 minutes and 35 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |



Summary
Fixed stop-ids-for-agency endpoint to return HTTP 404
when an unknown agency ID is provided instead of
HTTP 200 with a null body.
Problem
When an unknown agency ID is provided, the endpoint
was returning HTTP 200 with a null body instead of
a proper HTTP 404 response.
Changes
agency ID is not found in the transit graph
Testing
Before fix:
Request: GET /api/where/stop-ids-for-agency/999.json?key=test
HTTP Status: 200
Body: null
After fix:
Request: GET /api/where/stop-ids-for-agency/999.json?key=test
HTTP Status: 404
Body: {"code":404,"currentTime":1779991625902,"text":"resource not found","version":2}
Spec Reference
https://github.com/OneBusAway/maglev/wiki/stop-ids-for-agency
Proof
Closes #974