fleet-debugger
fleet-debugger copied to clipboard
googlemaps
The time range setting logic currently only considers updatevehicle log messages (ie lastUpdate & firstUpdate) it should also consider create trip logs.
The visualization is currently using the 'date' field from the log which corresponds to the time at which the server got the request. For retried requests we should consider only...
lodash memoize supports weakmaps so with a timerange key it might actually not cause memory bloat?
maybe plus a little buffer to show the end & beginning of the surrounding trips.
In general this repo uses camelCase. But a number of cases have snuck in. In particular use of APIKEY vs apiKey vs apikey.
They're different services ... it's unclear if we can continue ignoring that. There could be vehicle id conflicts.
Possible breakdowns: - offline vs online - trip status - whether on a trip or not
The combination of auth tokens is kind of confusing and what they are used for: * api key (for maps js sdk) * jwt (for journey sharing) * gcloud auth...
Code currently assumes server@... is used. That may not reflect either our current best practices documentation or what the customer has actually setup.
Performance is lagging even with only ~5 hours of updates. deck.gl should improve the performance of drawing header arrows and bubbles.