Closed rummik closed 2 weeks ago
You can handle this via custom rules. It would be nice if the addon had some more powerful ways of determining what project things should go to.
Custom rules require exposing full URLs to the API, which could be considered a major security risk if the URLs contain session or personal information
We could add the ability to call custom handlers to WakaTimeCore.sendHeartbeat.
Check if custom handler exists for given domain. If one exists, let that custom handler create the heartbeat payload data. Otherwise, use the default project and other heartbeat payload data.
Once custom handlers are working we can start adding custom handlers for any cloud IDE or websites we use.
There's a related conversation in #28. Until project detection from websites improves, custom rules are the only way to set projects for browsing activity.
For Mac, we're building this now into the desktop app. If anyone has a url they want supported please common on https://github.com/wakatime/macos-wakatime/issues/227.
Sites like GitHub, BitBucket, Travis-CI, ~Waffle.io~, and CircleCI, can contain the project name in the URL. It would be nice to be able to use that info without exposing the full URL to the WakaTime API