How-to guides

• Use a different logfile structure than the default
• End the application with different return codes
• Have a hidden option in a command
• Raise more informational errors
• Set a default command for the application
• Create unit tests for code that uses Craft CLI’s Emitter
• Define and use other global arguments
• Use the completion module
• Temporarily allow another application to control the terminal