Add configurable underscore command naming

[dereuromark]

Refs cakephp/cakephp#19086

Unfortunately, CakePHP's CommandCollection doesn't have a built-in mechanism to hide specific command aliases from the list - the hidden property on Command
classes applies to the command itself regardless of which name it's invoked with. Both will appear in bin/cake output, but both will work identically.

So we need a feature flag switch

Summary

• Add TwigView.useUnderscoreCommands config option for command naming style
• When true: registers twig_view compile (new underscore style)
• When false/unset: registers twig-view compile (deprecated hyphen style)
• Add config/app.example.php documenting available options
• Add PHPUnit 12 support

Upgrade path

1. Update scripts/CI to use twig_view compile
2. Set 'TwigView.useUnderscoreCommands' => true in config

We should be able to release this as a minor

[ADmad]

I doubt anyone is going to notice or use this config.

Another solution is adding both twig-view compile and twig_view compile and show deprecation warning when the old name is used. I checked and it works, only problem is the bin/cake only shows the dashed name twig-view compile in the help output regardless of the order in which the commands are added.

[dereuromark]

Yeah thats why the config: It allows the upgrade for those that want it, everyone else can safely ignore. No duplicate or weird display either way.

[ADmad]

But this config doesn't provide us a deprecation based upgrade path as we do for classes/methods, continue use of existing API with a deprecation while adding a new one.

[dereuromark]

As this is purely opt-in. If you think it is important you can also add a deprecation note of course to alert the user.

[othercorey]

Might be simpler to add both and just change it in a release.

[dereuromark]

Might be simpler to add both and just change it in a release.

I dont follow.

This PR seems ready and working as is IMO. Simple, yet effective, until next major.

[othercorey]

Do what you want then.

[dereuromark]

Do what you want then.

Can you explain what you mean with both? You want both parallel inside the CLI output for bin/cake?

[dereuromark]

Feel free to make an alternative PR if you do not want to move forward with this clear forward path solution.

Option	Approach	Pros	Cons
A	Config flag (current PR)	Clean, no duplicate output	Config unlikely to be used
B	Register both + deprecation	Standard deprecation path	Both show in bin/cake help (dashed name appears)
C	Register both, change default later	Simplest, no config	No deprecation warning

Option A for those that care, everyone else can continue to ignore until next major. Simple.

[othercorey]

I don't think it needs that much of a debate. The config is unlikely to be used, but no harm in adding it if you want a transition.

[dereuromark]

Yeah, agreed. Any way forward is good. Alternative PRs can be made if anyone feels strongly about it.