Current User Bundle Laravel Package

Product Decisions This Supports

• Build vs. Buy: Justifies buying this lightweight package over building a custom solution for fetching the current user in Symfony, especially for small-to-medium projects where reinventing the wheel isn’t a priority.
• Feature Roadmap: Accelerates development of user-specific features (e.g., audit logs, ownership tracking, or role-based access) by providing a standardized way to access the current user across the application.
• Use Cases:
  • Audit Trails: Automatically log who created/updated an entity (e.g., createdBy, updatedBy fields).
  • Role-Based UI: Dynamically adjust UI/UX based on the logged-in user’s permissions.
  • Multi-Tenant Apps: Track tenant-specific user actions without manual injection.
  • Legacy Migration: Quickly integrate user context into existing Symfony apps without refactoring.
• Technical Debt Reduction: Eliminates repetitive boilerplate code (e.g., manual SecurityContext checks) in controllers/services.

When to Consider This Package

• Adopt if:
  • You’re using Symfony 2/3 (last release in 2016, but core functionality remains relevant).
  • You need a simple, dependency-injection-friendly way to fetch the current user across services/entities.
  • Your team prioritizes maintainability over cutting-edge features (e.g., no need for Symfony 5+ compatibility).
  • You’re building CRUD-heavy apps where user context is critical (e.g., SaaS platforms, admin panels).
• Look elsewhere if:
  • You’re on Symfony 4/5/6+: Modern alternatives (e.g., Symfony’s built-in Security component or ParamConverter) may be better integrated.
  • You need advanced features (e.g., impersonation, multi-user contexts, or async user resolution).
  • Your app requires high scalability: The package’s age and lack of stars/activity suggest limited long-term support.
  • You’re using non-Doctrine ORMs (e.g., Eloquent in Laravel): This bundle is Doctrine-specific.
  • You need active maintenance: Consider forking or evaluating alternatives like Stof\DoctrineExtensionsBundle for similar functionality.

How to Pitch It (Stakeholders)

For Executives:

"This package lets us reduce development time by 20–30% for user-centric features like audit logs or role-based access. Instead of writing repetitive code to fetch the current user in every controller or service, we can standardize it with a single, battle-tested bundle. It’s a low-risk, high-reward decision—like adding seatbelts to a car: simple, safe, and saves time in the long run. The MIT license means no hidden costs, and the bundle’s focus on core functionality aligns with our goal of shipping features faster without technical debt."

For Engineering:

*"This bundle solves a painful but common problem: manually injecting the current user into services, entities, or controllers. Here’s why it’s worth adopting:

• Cleaner Code: Replace if ($this->getUser()) checks with a service (dyvelop.current_user.provider) or Doctrine annotations.
• Consistency: Standardize how user context is accessed across the app (e.g., article.createdBy always reflects the logged-in user).
• Zero Boilerplate: The Doctrine annotation (@Dyvelop\CurrentUser) auto-populates fields like updatedBy without lifecycle callback clutter.
• Symfony-Native: Works seamlessly with Symfony’s DI container and Security component. Tradeoff: It’s not actively maintained, but the core logic is stable and Symfony 2/3-compatible. If we hit limits, we can fork it or migrate to Symfony’s built-in tools later. Let’s prototype it in [Project X] to validate the win."*