Allow the wakatime api key to be persisted via settings sync

[randollrr]

I was about to create the very same issue. I only work in devcontainer (for a clean python env) and I have to re-enter the api key at every mod or new container image. If we can have it in the user/settings that will save me time.

[lablnet]

I use GitHub codespace Whenever I create new codespace I have to enter API key again and again which is just time wasting!

[alanhamlett]

I'll work on a PR for this. How about a checkbox to enable saving to vscode settings instead of the ~/.wakatime.cfg file?

[exil0867]

+1

[wvffle]

@alanhamlett How are the works on the PR?

[exil0867]

For those who use Devcontainers, you can bind .wakatime.cfg:

"runArgs": [
  "-v",
  "${env:HOME}/.wakatime.cfg:/root/.wakatime.cfg"
],

[mikebronner]

For those who use Devcontainers, you can bind .wakatime.cfg:

"runArgs": [
  "-v",
  "${env:HOME}/.wakatime.cfg:/root/.wakatime.cfg"
],

Which file is this to be added to? Trying to add it to devcontainer.json lints with "Property runArgs is not allowed."

[exil0867]

For those who use Devcontainers, you can bind .wakatime.cfg:

"runArgs": [
  "-v",
  "${env:HOME}/.wakatime.cfg:/root/.wakatime.cfg"
],

Which file is this to be added to? Trying to add it to devcontainer.json lints with "Property runArgs is not allowed."

Please check https://containers.dev/implementors/json_reference/#image-specific

[kotx]

@alanhamlett Is work still being done on a PR? If not I might be able to work on this

[alanhamlett]

@alanhamlett Is work still being done on a PR? If not I might be able to work on this

Not yet, so go for it 👍

[kotx]

Submitted a PR!