Translate API no longer requires an API key. #248
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
This was referenced Nov 16, 2016
bshaffer
approved these changes
Nov 16, 2016
| # Your Translate API key | ||
| $apiKey = 'YOUR_API_KEY'; | ||
| # Your Google Cloud Platform project ID | ||
| $projectId = 'YOUR_PROJECT_ID'; |
There was a problem hiding this comment.
Is the project ID required in lieu of an API key?
There was a problem hiding this comment.
Yes, typical of other cloud samples.
|
Will merge once tests pass |
|
Can you help me fix the test? I don't understand why it's failing. |
|
The linter complains about unused |
jmdobry
force-pushed
the
update-translate
branch
from
367127d
to
5119853
Compare
jmdobry
force-pushed
the
update-translate
branch
from
5119853
to
9c839cd
Compare
|
@jmdobry thanks Jason! |
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.
See