-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: allow for no gmaps_key input, add new parameters, fix .onLoad check #6
base: main
Are you sure you want to change the base?
Conversation
… ... + fix docs format (v0.1.2.9000)
thanks a thousand:) while you're doing it already, can you also adapt the readme and the website (under website/doc/Walkthrough/Walkthrough.md), then I can deploy the website change too. |
- remove the redundant ggmap::has_google_key() test, because even a wrong key will return TRUE. For a wrong key, the execution will be stopped with error message when the API test ggmap::geocode("US") fails. - use the check_gmaps_key alone to decide API key condition - apply quiet to all messages - styler:::style_active_pkg() - updated documentation
LGTM! |
Currently testing the integration in GL, because it throws error when running:
FYI @ArturoEsquerra @NicolasMatrices-v2 @JussanN @raphaeltamaki |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bernie, could you please check the comments on made on the PR before merging? I think there are a couple of things we should edit before landing.
…ion_to_cluster_match()
@NicolasMatrices-v2 please check. Thanks for your comments and feedback. I tend to avoid |
@NicolasMatrices-v2 @gufengzhou any updates here? Are we ready to merge after the changes suggested? |
commuting_zones()
without the need of fetching the coordinates using Google's API.devtools::check()