You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For print, it's hard to show both the model (which has field descriptions) and model schema view (which has examples and looks like JSON). How about a combined view, something like:
{
"values": [
{
"platform": {
"realtime_id": 0, // always zero
"stop": {
"suburb": "East Melbourne", // suburb stop is located
"transport_type": "train", // type of transport serving stop: train, bus, tram, vline, or nightrider
"stop_id": 1104, // unique identifier of the stop
"location_name": "Jolimont-MCG", // concise description given to stop
"lat": -37.81653, // latitude in decimal degrees
"lon": 144.9841, // longitude in decimal degrees
"distance": 0 // always zero
}
},
The text was updated successfully, but these errors were encountered:
Thank you, but I don't see ourselves supporting it. It's a bit of a personal preference as to how its represented, so we'll leave users to make the changes based on their needs.
For print, it's hard to show both the model (which has field descriptions) and model schema view (which has examples and looks like JSON). How about a combined view, something like:
The text was updated successfully, but these errors were encountered: