Which statement describes how to define a custom CLI flag for your generator?

Which statement describes how to define a custom CLI flag for your generator?

• A. this.defineFlag
• B. this.setFlag
• C. this.option
• D. this.addFlag

Answer: (C)

In a Yeoman generator, you define a custom CLI flag by using this.option in the generator’s constructor. This registers the flag with the CLI parser so users can pass it on the command line (for example, --name=value or --flag), and you can read the chosen value later from this.options.name. You can also specify the flag’s type, a default, and a description, such as this.option('dest', { type: String, desc: 'Destination folder', default: 'dist' }); Then you would use this.options.dest in your code to influence behavior. Other names like defineFlag, setFlag, or addFlag aren’t the standard API for declaring CLI options in Yeoman, while positional arguments would be defined with this.argument.

In a Yeoman generator, you define a custom CLI flag by using this.option in the generator’s constructor. This registers the flag with the CLI parser so users can pass it on the command line (for example, --name=value or --flag), and you can read the chosen value later from this.options.name. You can also specify the flag’s type, a default, and a description, such as this.option('dest', { type: String, desc: 'Destination folder', default: 'dist' }); Then you would use this.options.dest in your code to influence behavior. Other names like defineFlag, setFlag, or addFlag aren’t the standard API for declaring CLI options in Yeoman, while positional arguments would be defined with this.argument.