Bug: routes.some is not a function

[mattwalo32]

I was using the site and it crashed with this error:

Which corresponds to this snippet:

I opened the network tab and looked at the response from the /stations endpoint. Out of the 1123 stations returned, 6 of them had their routes field set to an empty string instead of an array. For example, here's a response for one of the stations in the returned body:

{
  "city": "Orlando",
  "code": "MCO",
  "connections": "",
  "id": "MCO",
  "lat": 28.41453,
  "lon": -81.30818,
  "name": "Orlando Station",
  "nearbyCities": "",
  "routes": "",
  "stateLong": "Florida",
  "stateShort": "FL",
  "thruway": false,
  "frequency": 0
}

This doesn't happen consistently, only sometimes. I was going to put up a PR but seems like this is more of a backend issue, which I don't see a repo for.

[Mr-Technician]

Thanks for letting me know, I am on vacation and was adding some stations from my Amtrak train, and accidentally broke this. I fixed it promptly as soon as I received an email about the issue. The frontend needs a fix so this doesn't break if the routes are missing so I'll keep this open for now.