Add support for using a Google API key. #18
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Nice one! Thanks!!! |
|
As soon as GitHub figures itself out, I will merge. GH seems to be stuck. |
|
Cool. I'm glad I could help. On Thursday, September 20, 2012 at 12:21 PM, Chris Le wrote:
|
chrisle
pushed a commit
that referenced
this pull request
Oct 1, 2012
Add support for using a Google API key.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow a Google API key to be used for requests, which greatly raises the allowable rate limits. The rate limits for anonymous requests are pretty low.
This addresses Issue #17.