composeWith ignores priority groups when force is added as an option and force is ignored in the CLI.

[Aerex]

From what I understand about composeWith, the method follows the priority group execution in the runLoop. For instance, if you call composeWith under install the composed generator and main generator should call install and any priority group lower (e.g. end).

This behavior seems to be ignored if the force option is passed in like the following:

 this.composeWith(require.resolve('../turbo'),{ force: true});

In addition, if you call the generator in the CLI and pass the force option like so

yo generator-something  --force true

The prompt still asks if you want to overwrite which shouldn't given the option.

I have two questions. Is there a way where we can attach an EventEmitter to the IO procedures so that if a copying fails or does not happen (a priority group is not run) the user knows about it?

[github-actions]

This issue is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 5 days