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
In order to progress to V1 this feature is tracking the changes needed to the way mock data is being handled. Especially for demo purposes the initial page after login uses the current users geolocation and all mock data is added using the app/lib/data/mock_travel.json which requires a re-build and re-deployment of the application.
This should be handled in the admin section so as to make it easier to change the mock data for different demos.
Given the TOS limitations of Google Maps to be pull the geo coordinates of a polylines drawn on the map this will have to be a simple text field where the data is copied / pasted into. This may require a change to the database, either a new datastore collection or investigate if moving to an AlloyDB db is worth it?
The text was updated successfully, but these errors were encountered:
In order to progress to V1 this feature is tracking the changes needed to the way mock data is being handled. Especially for demo purposes the initial page after login uses the current users geolocation and all mock data is added using the
app/lib/data/mock_travel.json
which requires a re-build and re-deployment of the application.This should be handled in the admin section so as to make it easier to change the mock data for different demos.
Given the TOS limitations of Google Maps to be pull the geo coordinates of a polylines drawn on the map this will have to be a simple text field where the data is copied / pasted into. This may require a change to the database, either a new datastore collection or investigate if moving to an AlloyDB db is worth it?
The text was updated successfully, but these errors were encountered: