Tag Debug Laravel Package

Product Decisions This Supports

• Debugging & Observability: Enables deeper visibility into Symfony service tags, aiding in debugging complex service dependencies, circular references, or misconfigured tags.
• Developer Productivity: Reduces manual inspection of container configurations by programmatically querying tagged services, accelerating troubleshooting.
• Maintenance & Refactoring: Supports auditing tagged services (e.g., monolog.logger, twig.extension) during refactoring or dependency updates.
• Build vs. Buy: Justifies a lightweight, open-source solution over custom tooling for Symfony-based projects needing tag inspection.
• Roadmap Alignment: Useful for teams adopting Symfony or Laravel (via Symfony components) where service tags are heavily used (e.g., event listeners, compiler passes).

When to Consider This Package

• Symfony/Laravel Ecosystem: Only relevant if your project uses Symfony’s Dependency Injection Container (DIC) or Laravel’s underlying Symfony components (e.g., ContainerBuilder).
• Debugging Scope: Limited to inspecting tagged services—not general container debugging (e.g., service IDs, parameters). For broader inspection, consider symfony/var-dumper or symfony/profiler.
• Outdated Maintenance: Last release in 2014; evaluate risk for projects requiring long-term support. May need forks or wrappers for modern Symfony/Laravel versions.
• Alternatives Exist:
  • Use Symfony’s built-in debug:container CLI command for basic inspection.
  • Leverage IDE tools (PHPStorm’s Symfony plugin) for visualizing services.
  • Consider symfony/dependency-injection + custom scripts for advanced use cases.
• Filtering Needs: Only useful if you need programmatic filtering of tagged services (e.g., by service name, class, or custom criteria).

How to Pitch It (Stakeholders)

For Executives: "This lightweight library provides a programmatic way to audit and debug Symfony service tags—critical for maintaining complex applications built on Symfony/Laravel. It reduces manual configuration checks during debugging, speeds up troubleshooting, and aligns with our use of Symfony’s DI container. The MIT license and open-source nature eliminate licensing costs, while the minimal overhead makes it a low-risk addition."

For Engineering/DevOps: *"TagDebug lets us programmatically inspect tagged services (e.g., event listeners, compiler passes) in Symfony’s DIC, which is invaluable for:

• Debugging: Quickly identify which services are tagged with monolog.logger or twig.extension during runtime issues.
• Refactoring: Audit dependencies before breaking changes (e.g., renaming tags or services).
• CI/CD: Add automated checks for tagged service consistency in pipelines. Tradeoff: It’s Symfony-specific and unmaintained, so we’d need to test compatibility with our version. For broader needs, we might pair it with Symfony’s CLI tools or IDE plugins."*

For Developers: *"If you’re working with Symfony’s service tags and tired of manually grepping services.yaml or config.php, this library lets you fetch and filter tagged services via code. Example:

$tags = (new TagFetcher($container))->fetch(new FilterList([new Name('logger')]));

Pros: No CLI dependency, extensible filters. Cons: Old (2014), so test thoroughly. For modern Laravel, check if it works with symfony/dependency-injection."*