Question 1

How to create a subcommand in Minicli?

Accepted Answer

Use command namespaces by organizing controllers in directories under app/Command, such as app/Command/Help for 'help' subcommands. Each controller class handles specific subcommands, as shown in the structured app template.

Question 2

Minicli vs Symfony Console: which should I use?

Accepted Answer

Choose Minicli if you prioritize minimal dependencies and lightweight structure for simple to medium CLI tools. Symfony Console is better for complex applications needing rich features, extensive community support, and integration with Symfony components.

Question 3

Can I use Minicli with Laravel?

Accepted Answer

Yes, but it requires manual integration since Minicli is standalone. You may need to bootstrap it separately within a Laravel project, which can add complexity compared to using Laravel's built-in Artisan commands.

Question 4

How to add custom colors or themes in Minicli?

Accepted Answer

Create a custom theme by extending the DefaultTheme class and overriding the getThemeColors method, then set it in the App configuration. The README provides an example BlueTheme in the 'Color Themes' section.

Question 5

Is Minicli good for building interactive CLI tools?

Accepted Answer

Minicli handles basic user input with the readline extension, but for highly interactive tools with menus or wizards, you may need to implement additional logic, as it lacks built-in interactive components like prompts or selectors.

Question 6

How to handle command arguments and options in Minicli?

Accepted Answer

Arguments are accessed through the CommandCall object in command callbacks or controllers, which parses input parameters. You can define and process them manually, as seen in the minimalist app example with var_dump($input).

Minicli

What is Minicli?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions