Replies: 2 comments 2 replies
-
|
Hey @Zlendy , thats fine, it doesn't need to be a component in jellystat since the api can be used externally |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Moved to PR #378 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'd like to make a PR to implement a new API endpoint (
/stats/getViewsByLibraryType) that aggregates playback count by its type (instead of using individual libraries) and use that to integrate some statistics provided by this service into a Homepage Widget.This endpoint should accept
daysas a query parameter and return a JSON similar to this:{ "music": 1, "movie": 2, "episode": 3, ... }Although the original purpose of this endpoint is not to be consumed directly inside Jellystat, I'd have no problem with making a new component to consume this data in-app.
I'm making a discussion first to hear your thoughts before I start working on something you may not want to have inside your codebase.
Beta Was this translation helpful? Give feedback.
All reactions