Add VSCode setting for API key #318
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
|
Let's not set it by default from the prompt, only when set in the settings directly. Otherwise, a lot of people not running in dev containers will get confused when their vscode api key becomes out of sync with their |
|
@alanhamlett Should be fine now! |
alanhamlett
approved these changes
Jan 13, 2023
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.
Resolves #283.
I was not able to test it for the VSCode Web extension, but in theory it should work.
Here's what it looks like:
Now setting the API key from the prompt (
WakaTime: Api Keycommand) will also set it in VSCode global settings. Let me know if this should not be the case.VSCode Settings Sync is also enabled for the API key.