✨ feat(wakatime): new features and fixes

[iammola]

Description

• Added Pagination to Leaderboards.
• Added Details to User's Activity Change.
• Replace user's email with timezone in accessory.
• Allow use of extension without apiKey in some commands.
• Fixed Sorting of Recent Projects.
• Fixed NaN% in activity change.

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[iammola]

Since I made this optional, I had to repeat it in the summary and private-leaderboards commands that require it.

I don't know if there's a better way of handling this, because I expected the apiKey preference to be shared across all commands. But adding it to one command doesn't apply it to the others/entire extension.

[sxn]

Unfortunately there's no current way of defining a per-extension required preference and make it not required for a particular command, so I guess this is the only way to go about it currently.

You can define a per-extension preference, the way you did here, make it required, and then re-define it in a particular command and set it to required: false in that particular command. So your package.json would look like this:

…
  "preferences": [
    {
      "name": "apiKey",
      "required": true,
      "title": "WakaTime API Key",
      "type": "password",
      "description": "Use your WakaTime API key to use your account",
      "placeholder": "Enter your API key from https://wakatime.com/settings"
    }
  ],
  "commands": [
…
    {
      "name": "leaderboard",
      "subtitle": "WakaTime",
      "title": "Show Public Leaderboard",
      "description": "An overview of the public leaderboard. Check your rank against others all around the world.",
      "mode": "view",
      "preferences": [
        {
          "name": "apiKey",
          "description": "Use your WakaTime API key to use your account",
          "type": "password",
          "required": false,
          "title": "WakaTime API Key"
        }
      ]
    },
…

[iammola]

This works! My only problem is the user still has to provide the API key for that command as well. It's still better than the way I had it before, because now it's only one other command that asks for it.

Just to be sure, is there a way to set the preference programmatically? I checked but didn't find anything. @sxn

[sxn]

is there a way to set the preference programmatically?

Not yet, but it's been requested before, so we may end up looking into it.

the user still has to provide the API key for that command as well

do you mean the fact that the field still appears in preferences for that particular command? or something else?

The current version of the branch works as follows for me:

Screen.Recording.2022-10-27.at.13.21.55.mov

[iammola]

That's not my direct problem with it, but yeah I'll like for the same API key to be used across the extension and updating in the public leaderboard won't update the extension-wide one.

Its not a critical issue so can you please re-review the changes? Thanks!

[stale]

This issue/pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs in the next 7 days to keep our backlog clean. Thanks for your contributions.

[sxn]

🎉

[raycastbot]

Published to the Raycast Store:
https://raycast.com/iammola/wakatime