Closed ttavenner closed 10 years ago
Create a branch off master now called google geocoding or some such and then do smarty streets on master.
On Sunday, May 4, 2014, Tommy Tavenner notifications@github.com wrote:
I'm planning to implement SmartyStreets, now that we have it, rather than Google. Should I create a separate branch for SmartyStreets and keep the Google API version? It would make the code more accessible since not everyone will have SmartyStreets access but everyone will have Google access.
— Reply to this email directly or view it on GitHubhttps://github.com/c4hrva/open-health-inspection-scraper/issues/11 .
Or better yet just tag the last commit before you start smarty streets. We probably won't continue to support the google geocoding branch.
On Sunday, May 4, 2014, Ben Schoenfeld ben.schoenfeld@gmail.com wrote:
Create a branch off master now called google geocoding or some such and then do smarty streets on master.
On Sunday, May 4, 2014, Tommy Tavenner notifications@github.com<javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:
I'm planning to implement SmartyStreets, now that we have it, rather than Google. Should I create a separate branch for SmartyStreets and keep the Google API version? It would make the code more accessible since not everyone will have SmartyStreets access but everyone will have Google access.
— Reply to this email directly or view it on GitHubhttps://github.com/c4hrva/open-health-inspection-scraper/issues/11 .
Good thought. Done.
I'm planning to implement SmartyStreets, now that we have it, rather than Google. Should I create a separate branch for SmartyStreets and keep the Google API version? It would make the code more accessible since not everyone will have SmartyStreets access but everyone will have Google access.