John Kwening

@turisap certainly, go for it. It's assigned to you. Thanks.

@turisap we have a service worker implemented, so its probably caching the main bundle.js module where the primary code logic is embedded. You probably just need to set the service...

@turisap sorry for just getting back to you - completely missed this in my inbox. Here's my response in order of your questions: - Regarding style - give the following...

@turisap I've create a feature branch called "place-details" that we will use for this issue until its complete and ready to be merged into "development" branch. Did my response answer...

@turisap regarding requests to the backend server, you're heading in the right direction; please utilize `makeRequest()` function along with `BASE_ENDPOINTS` object in `server-request-utilities.js` (see PR #264 OnLocationFound() and saveSaveMarkerToDB() functions...

This is issue is becoming more of a priority since the frontend is now setup to make requests to the backend server. We need to standardize how we send response...

@motosharpley yep - agreed on the catch-all for server app.js. I'm still trying to track down how the server is crashing at certain times due to uncaught error that I...

@redragonx yep - multiple commits/PR is definitely fine and encouraged...I'm definitely big fan of piecemeal implementation and updates than one massive code update which can be tricking to test and...

@redragonx the status code constants I was thinking something like this: ``` export const STATUS = { "OK", "UNKNOWN_ERROR", "NOT_FOUND", "REQUEST_DENIED", "INVALID_REQUEST", "ZERO_RESULTS", } ``` So that the same status...

@redragonx glad to hear you're making progress. We're working out of a feature specific branches, so feel free to make PR request as you have parts of it committed and...