{"push_id":1409925334,"size":1,"distinct_size":1,"ref":"refs/heads/randomRestaurant_SlotMachine_redesign_1.0","head":"0decd8aa371e7c1b0f56bbaa93bee857ccf0267c","before":"a51b670a8efa1803525a9453a1f87cc4ce1b5217","commits":[{"sha":"0decd8aa371e7c1b0f56bbaa93bee857ccf0267c","author":{"name":"zuchie","email":"3f1bc3e9de627a6f6168fec86e606471f61e0540@gmail.com"},"message":"1. Changed back to show search results in same table view instead of using a separate result table view controller.\n2. Used native location manager to get current location coordinates instead of using Google Places API because the latency was big some times.\n3. Chosen locations from Google Places Autocomplete won't give coordinates, in order to get coordinates to match current location, use Google Place Details API to get Location coordinates from its placeID which could get from autocomplete.\n4. Used Type Properties for YelpUrlRequestParameter class so that it doesn't need to instantiate class and pass its stored properties in every View. And Type Properties could be assigned anytime to make multi-threading easy to work, e.g. main thread can keep going and thread of getting coordinates from placeID by Google Place Details API can assign type properties coordinates anytime when Google Places API web service responses. It has to wait for the response before it segues to next view previously.","distinct":true,"url":"https://api.github.com/repos/zuchie/randomRestaurant/commits/0decd8aa371e7c1b0f56bbaa93bee857ccf0267c"}]}
{"actor":{"display_login":"zuchie"}}