"Stations connected to" endpoint?

[joecorcoran]

Hey there,

Thanks so much for all the incredibly useful VBB libraries, and especially for running this REST API!

I wondered if you'd be interested in this API having an endpoint exposing the data in vbb-stations-connected-to – maybe at GET /stations/:id/connected-stations or similar.

I'm using the connected stations data in a single-page app and at the moment my only options are to 1. include the huge blob of data as JavaScript (very large, makes my app > 1 MB) or 2. run my own API exposing only this data, and have my app make requests to two different APIs.

I'd be up for doing the implementation if you don't have time. I just wanted to check here before doing any work on it. Maybe there are design/performance reasons why you don't want to do this, I'm not sure.

[derhuerst]

I wondered if you'd be interested in this API having an endpoint exposing the data in vbb-stations-connected-to – maybe at GET /stations/:id/connected-stations or similar.

Definitely! This would be a very useful feature. Pull request welcome!

The only caveat I see is that vbb-stations-connected-to might become outdated if i forget to update it. But this applies to all other vbb-* dependencies that this API uses, so I'd say that's negligible.

[...] include the huge blob of data as JavaScript (very large, makes my app > 1 MB) [...]

I also think that vbb-stations-connected-to can be made smaller if we store the original IDs only once and use placeholder IDs.

[joecorcoran]

Great! I'll post again here when I've got started.

I also think that vbb-stations-connected-to can be made smaller if we store the original IDs only once and use placeholder IDs.

Agreed. I can take a look at this at the same time.