You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @shyim, thanks for bringing this up! Supporting the durations API would definitely improve compatibility between Wakapi and WakaTime.
I'll keep this open as a feature request, but, realistically, this won't be implemented any time too soon. Implementing the API itself would be quite straightforward, but durations in Wakapi work a bit differently than in WakaTime, which we would have to account for.
Also, the concept of durations is a somewhat internal thing anyways. A user shouldn't ever have to deal with "raw" durations, but would rather be interested in summarized statistics.
I looked into the plugin's code, and it seems like the only purpose for using the durations endpoint is to fetch today's total coding time - without any need for the actual level of granularity that the endpoint provides. So my suggestion would be to open a PR with the plugin where the durations endpoint gets replaced by the stats endpoint. This would not only make the plugin compatible with Wakapi, but also improve efficiency, because it wouldn't have to download a whole batch of duration objects just to get a single number (total time) in the end.
Hi, this endpoint could be really useful. It can be used by clients to show what a user worked on the day, the pauses it took, etc.
A user shouldn't ever have to deal with "raw" durations, but would rather be interested in summarized statistics.
I wouldn't say that this is raw data, the funny thing is that heartbeats (which are literally the raw data) is exposed via the API, but durations are not.
Hey,
I want to get a Streamlabs Plugin to run, but it seems like the Duration API is not supported right now.
Client code to call
The text was updated successfully, but these errors were encountered: