Refactor repositories and services to support cumulative activity counts and improve dashboard UI

[Ziedelth]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @Ziedelth, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a comprehensive refactoring of the application's analytics and member activity tracking systems. It shifts data aggregation responsibilities to the persistence layer, enabling more efficient retrieval of cumulative activity counts. Concurrently, the administrative dashboard's user interface, particularly the member details view, has been significantly upgraded to present this richer data in a more organized and visually appealing manner, enhancing administrative oversight and user experience.

Highlights

• Backend Refactoring for Cumulative Counts: The core logic for calculating activity metrics has been moved from service layers to repository layers. New repository methods now directly compute cumulative counts for member logins, followed animes, and followed episodes, as well as detailed user analytics (returning users, app versions, locales, devices).
• Granular Analytics API Endpoints: The /admin/api/analytics endpoint has been split into more specific endpoints: /metrics, /attachments, and /users. This provides a more organized and efficient way to retrieve different types of analytics data.
• Enhanced Member Dashboard UI: The member edit page (/admin/members/edit.ftl) has undergone a significant visual overhaul. It now features a structured dashboard layout with improved profile information, dedicated activity overview charts, and redesigned sections for followed animes and recently watched episodes, offering a more intuitive and informative experience.
• Simplified Frontend Data Handling: The JavaScript code for dashboard charts (dashboard_chart.js and within edit.ftl) has been refactored to consume the new, pre-aggregated cumulative data directly from the API. This simplifies client-side logic and improves chart rendering efficiency.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request is a significant improvement, refactoring analytics endpoints for better performance and clarity, and overhauling the dashboard UI. The shift of data aggregation logic to the repository layer is a great move. My feedback focuses on further optimizing performance in a few controller methods and enhancing maintainability in the repositories by reducing code duplication. Overall, these are excellent changes.