🧹 Centralize Pro role check in ReportsController#3
Conversation
This commit centralizes the Pro role check by: 1. Adding an `isPro()` method to the `User` model. 2. Creating an `EnsureUserIsPro` middleware to handle Pro-only access. 3. Registering the `pro` middleware alias in `bootstrap/app.php`. 4. Refactoring `ReportsController` to use the new middleware for export methods. 5. Updating `CategoryController` and `SubscriptionLimitService` to use the `isPro()` helper for consistency. This reduces code duplication and ensures a consistent authorization logic across the application. Co-authored-by: RabbitVisual <94582877+RabbitVisual@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Auto-merged via Jules AI Workflow
1 participant
Centralized the Pro role check (pro_user or admin) by adding a helper method to the User model and a dedicated middleware. Refactored ReportsController and other components to use these new centralized tools.
PR created automatically by Jules for task 3116180519022258672 started by @RabbitVisual