-
Notifications
You must be signed in to change notification settings - Fork 147
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
Leverage User Settings #44
Comments
The reason we use |
Ah, that makes sense.
|
Any more thoughts on this one, @alanhamlett ? |
That's doable, we could even only prompt for specific setting keys that are found in both |
@alanhamlett - Awesome! It seems like I'm asking a lot of you lately. :) |
What's the status of this issue @alanhamlett? |
@alanhamlett Currently we have shared remote workspaces (for Remote SSH to connect), thus it is necessary for us to have WakaTime reading the settings using the VSCode settings mechanism. Also we need to have the option to disable |
is that a feature already inmplemented/needed @alanhamlett? |
If we pass |
It won't complain about missing config file unless you provide |
OS: Windows 10 1706 / Ubuntu 16.04
vsCode Version: 1.20.1
Plugin Version: 1.1.22
Issue
I think that this plugin should leverage User Settings to store configuration options such as the APIKey and Status Bar Icon. This would be convenient, and allow for easier syncing.
The text was updated successfully, but these errors were encountered: