MindBlockLabs/mindBlock_app

AI Summary: Implement a singleton Redis client in a NestJS application using a custom module, making it injectable across all modules for caching and other operations. This involves creating a provider, module, and injection token, handling connection lifecycle, and integrating with the application's configuration.

AI Summary: Implement an AchievementUnlocker provider in a NestJS backend to handle achievement unlocking based on puzzle completion milestones. This involves defining unlock rules for achievements like "Mind Master" (50 logic puzzles solved), "Perfect Streak" (10 consecutive puzzles solved without errors), and "Top 100" (reaching the top 100 leaderboard rank). The provider will be called from relevant services to check and assign achievements after puzzle submission.

AI Summary: Create a new database entity called `PuzzleEvent` in a NestJS/TypeORM project. This entity will log user actions such as puzzle completion, token awards, and achievement unlocks. The entity will include fields for user ID, event type, description, and timestamp.

AI Summary: Create a new REST endpoint `/users/:id/activity` that returns a paginated list of a user's recent activities (puzzle completions, achievements, etc.) This requires creating a new provider to fetch and format the data from the PuzzleEvent repository using pagination and sorting, and integrating this provider into a controller to expose the endpoint. The response should be a user-friendly array of activity descriptions and timestamps.

AI Summary: This task requires adding a 'category' field to the puzzle/IQQuestion database entity, tracking puzzle progress by category, and creating a new API endpoint to retrieve user progress categorized by (logic, coding, blockchain). This involves database schema changes, updating data persistence logic, creating a new service/provider for progress tracking, implementing a new API endpoint, and writing integration tests.

AI Summary: Create a new `Achievement` entity in a NestJS/TypeORM project, including fields for id, title, description, icon URL, and an optional unlock condition. Implement a many-to-many relationship between `Achievement` and `User` entities, and then generate and run a database migration to update the PostgreSQL schema.

AI Summary: Refactor the existing LeaderboardService in a NestJS backend application to improve code organization and maintainability. This involves creating four new provider classes (LeaderboardFetcher, LeaderboardStatsUpdater, UserRankCalculator, LeaderboardTimeFilter) to handle distinct responsibilities within the leaderboard functionality, injecting these providers into the LeaderboardService, updating the LeaderboardController to use the new providers, and ensuring all existing unit tests continue to pass.

AI Summary: Create a new API endpoint (/analytics/breakdown) that returns the count of different event types (e.g., question_view, answer_submit) from the analytics data. The endpoint should support filtering by date and user ID, using existing filtering mechanisms. The response should be an array of objects, each containing an event type and its count. Swagger documentation should be updated to reflect this new endpoint.

AI Summary: Develop admin-only REST endpoints for managing IQ questions within the Mind Block backend application. This includes creating, reading, updating, and deleting questions, ensuring proper input validation using DTOs, implementing role-based access control, updating Swagger documentation, and writing unit and integration tests.

AI Summary: Implement Role-Based Access Control (RBAC) in a NestJS backend application. This involves creating a UserRole enum, a RolesGuard using NestJS's CanActivate interface, a custom @Roles() decorator, integrating with the existing authentication flow to add role data to req.user, applying the decorator to admin-only routes (e.g., for managing IQ questions), and ensuring unauthorized users receive a 403 Forbidden response. Thorough testing is required.

AI Summary: Implement an API endpoint that allows administrators to export filtered analytics data as a CSV file (and optionally PDF). This involves creating a new GET endpoint, handling existing filter parameters, formatting data for CSV export using a library like `fast-csv`, setting appropriate HTTP headers for file download, and enforcing administrator access using role-based access control (RBAC). Swagger documentation should also be updated.