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
refactor: remove hardcoded google api key #15478
Conversation
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.
Was the GOOGLEAPIS_ENDPOINT
definition from he removed header not used anywhere?
docs/api/environment-variables.md
Outdated
webservice. Because this API key is included in every version of Electron, it | ||
often exceeds its usage quota. To work around this, you can supply your own | ||
Google API key in the environment. Place the following code in your main process | ||
You can supply your own Google API key in the environment. Place the following code in your main process |
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.
This loses the context that the previous revision had of "what is this key for."
Maybe something like
You can provide an API key for making requests to Google's geocoding webservice. To do this, place the following code in your main process
@ckerr |
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.
LGTM
Release Notes Persisted
|
Description of Change
Remove hardcoded Google API key as current pricing tiers and requirements have precluded it from working in a free capacity for quite some time. Update documentation to reflect that it must now exclusively be passed in via env var.
/cc @zcbenz
Checklist
npm test
passesRelease Notes
Notes: remove hardcoded Google API key