Console Laravel Package

Product Decisions This Supports

• CLI Tooling Roadmap: Accelerate development of internal CLI tools (e.g., data migration scripts, admin utilities, or DevOps workflows) by reducing boilerplate and enforcing type safety.
• Build vs. Buy: Avoid reinventing Symfony Console wheel while gaining stricter input validation and cleaner interfaces (e.g., IO object vs. Input/Output/SymfonyStyle).
• Use Cases:
  • Internal Developer Tools: Replace ad-hoc scripts with maintainable, typed CLI commands (e.g., app:generate-report, app:clean-cache).
  • Admin Interfaces: Build lightweight CLI dashboards for non-web tasks (e.g., user management, batch processing).
  • Testing Infrastructure: Leverage the IO object’s typed API to validate CLI interactions in automated tests (reduces flakiness).
  • Standalone Applications: Package CLI tools as reusable PHP libraries (e.g., composer require vendor/cli-tool) without Symfony overhead.

When to Consider This Package

• Adopt if:
  • Your team uses Symfony Console but wants stronger typing (e.g., asStringNonEmptyList(), asNullablePositiveInteger()) to catch errors early.
  • You need cleaner interfaces (e.g., IO object instead of Input/Output/SymfonyStyle triad) to reduce cognitive load.
  • Your CLI tools require dependency injection (e.g., injecting UserManager into commands) and service container access.
  • You’re building internal tools where maintainability > framework features (e.g., no need for hidden commands or aliases).
• Look elsewhere if:
  • You need Symfony Console’s full feature set (e.g., hidden commands, aliases, or Application methods like getHelp()).
  • Your project is non-Symfony and requires a zero-dependency solution (e.g., symfony/console or bobthecoder/symfony-console).
  • You prioritize active maintenance over a lightweight, MIT-licensed package (this has 19 stars but no dependents).
  • Your CLI tools are simple (e.g., one-off scripts) and don’t justify the abstraction layer.

How to Pitch It (Stakeholders)

For Executives:

"This package lets us build reliable, maintainable CLI tools faster by reducing boilerplate and adding type safety. For example, instead of writing fragile scripts, we can create commands like app:generate-report with validated inputs (e.g., asPositiveInteger()) and dependency injection. This aligns with our goal of [X initiative] by cutting dev time for internal tools and improving error handling. The trade-off is minimal—we’re not adding new dependencies, just swapping Symfony Console’s verbose API for a cleaner one."

For Engineers:

*"Pros:

• Stronger typing: Input validation at parse time (e.g., asStringNonEmptyList() rejects empty strings).
• Cleaner API: IO object consolidates Input, Output, and SymfonyStyle into one typed interface.
• Symfony-compatible: Works with FrameworkBundle or as a standalone tool.
• Test-friendly: IO mocking is easier with typed methods (e.g., getTypedArgument()).

Cons:

• Missing some Symfony features (e.g., hidden commands, aliases).
• Smaller community (19 stars, 0 dependents) but MIT-licensed and actively updated.

Use Case: If you’re building CLI tools for [Y project], this cuts 30% of boilerplate and adds safety nets. Example:

// Before (Symfony Console)
$username = $input->getArgument('username'); // No type checking!
if (empty($username)) { /* handle error */ }

// After (fidry/console)
$username = $io->getTypedArgument('username')->asStringNonEmptyList();
// Throws exception if empty or not a string.
```*
**Ask**: Should we adopt this for [Z initiative] or wait for [alternative]?"*