Add JavaScript / Deno support #81
Conversation
todo: test code
…ealtime-bindings into add_deno_support
|
|
| console.log(feed); | ||
| console.log(feed.entity[0].vehicle); | ||
|
|
||
| // todo |
| console.log(feed); | ||
| console.log(feed.entity[0].vehicle); | ||
|
|
||
| // todo |
|
|
||
| ## Regenerate the language binding source from gtfs-realtime.proto. | ||
|
|
||
| 1. make nodejs/gtfs-realtime.js and edit as ES module |
There was a problem hiding this comment.
Due to the overhead of maintaining bindings in multiple languages, we've been shying away from adopting any new languages where the update process can't be automated. It looks like this updating process requires hand-editing to update the bindings? More details here are needed.
@maximearmstrong would need to weigh in on MobilityData's willingness to take on the additional responsibility of manually updating these bindings going forward.
Related - we should update the "Other languages" section of the README to more specifically itemize the requirements for new binding language contributions (e.g., supported by official PB tooling, process to update and publish release can be automated).
No description provided.