Bryan

@jkwening we should make a new branch I just created that gmap-places branch to preserve the code from the google implementation before refactoring it out for leaflet in case someone...

I like the idea of having a standardized set of responses I would also like to see a catch-all in app.js that would handle anything that manages to fall all...

here is a little snippet of a catchall to help get you started ``` / error handling app.use((req, res, next) => { const error = new Error('Not found'); error.status =...

if you scroll down a bit this thread has examples of different approaches, synchronous, event etc. https://stackoverflow.com/questions/7310521/node-js-best-practice-exception-handling

@redragonx you can use postman to hit the endpoints and test to see that your getting the expected response back https://www.getpostman.com/

@jose8a we are using plain old vanilla css so the context might feel a little different but it's not so bad really, we would be stoked to have your help!...

@jkwening one thing I noticed looking at this tonight too is that when the marker is moved while offline the directions pane is lost so we may need to figure...

@thesparrow please coordinate with @tanyagupta she has started on this however there is more to do if you would like to help. Also your team invite is still pending, once...

We can use this as a master ticket and reference other smaller issues that need more description and are able to be completed in isolation. I will have to to...

Here is a starting point for this https://developer.mozilla.org/en-US/docs/Web/API/Detecting_device_orientation and this is a good application summary https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Orientation_and_motion_data_explained