-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activity Page does not support Filtering and Pagination together correctly #6221
Comments
That means filtering should be done first before pagination, right? |
It's definitely not ideal, but this is currently working as intended. Pagination happens on the backend because the query can be slow (I have 126,000+ entries on my main server) and filtering happens on the frontend because the api does not support filtering. We might be able to add some logic to fetch additional rows if filtering results in less than the page size but that doesn't appear to be something that is supported "out of the box" with the table library. |
When you say the API doesnt support it, do you mean the Jellyfin server API doesnt have a filter option on the query? |
The user activity API in the Jellyfin server does not support filtering. |
So what we have to build anyways(filtering?), like give some hints to do it |
So from what I can see it has Date and UserId filtering |
Just thinking about working on this and adding filtering server-side, however it might be slow to return results if the Activity Logs are big since the Type is stored as a string unless we add an index on the type. Is it worth it to add Type and Level filtering server-side if an index is required? |
This is not correct. You can only currently filter on system vs user events and get the activity since a specific date. |
The suggestion is to add Type and Level filtering on the server-side. |
It might be a bit too complex to implement the required functionality to make it work on web as we'd need support for both sorting and filtering (for all columns) by query. |
I don't mind giving it a try. Material React Table being used seems to support server-side querying and filtering. |
Describe The Bug
The Activity Page does not support Filtering and Pagination together due to doing pagination on server side, and filtering on the client side.
This means If you set a filter for a user, it only filters the results on the current page you are on.
e.g. Page1 may return 0 results, Page 2 may return 2 results, page 3 5 ect.
Steps To Reproduce
This is demenstrated best on an account that doesnt use jellyfin often
Screenshots
Page 1
Page 2
System (please complete the following information):
The text was updated successfully, but these errors were encountered: