Today DC’s 311 service started resetting connections instead of responding to requests, and our service just rendered Internal Server Error pages. This is understandable (and as designed) — but let’s do better.
This PR introduces an error page to handle when we cannot reach DC311’s API.
Additionally, this PR adjusts the tests for DC311.getServiceRequests() to not be dependent on today’s date, which enables the generated fixture files to fully handle the tests, preventing any network requests when running npm test.
Today DC’s 311 service started resetting connections instead of responding to requests, and our service just rendered
Internal Server Errorpages. This is understandable (and as designed) — but let’s do better.This PR introduces an error page to handle when we cannot reach DC311’s API.
Additionally, this PR adjusts the way we extend
Errordue to https://github.com/babel/babel/issues/3083 (theinstanceofoperator wasn’t working correctly before).Additionally, this PR adjusts the tests for
DC311.getServiceRequests()to not be dependent on today’s date, which enables the generated fixture files to fully handle the tests, preventing any network requests when runningnpm test.