Mark Scherer

Not with the right ruleset. It often happens that the type is customized. The variable must match at least.

I think it should be kept this way. But: One could follow my earlier tip and approach ( https://github.com/cakephp/bake/pull/365/files ) to make the configs Configure defaultable. As such everyone can...

No, I only applied my configure approach to one specific flag. I recommended to do that for all.

Anyone interested in a PR that would allow setting more global personal defaults? That would solve this per person/preference. The default of having the tests and fixtures right away still...

ping @HumanG33k

We could try to look up based on the class, and otherwise just default to text or some default that will always work? Better than failure maybe?

I also disagree with this. It adds a complexity and other pitfalls. Instead, one should have committed the files (via Git for example), and then can easily run -o (overwrite)...

> using the --force option oh, yes, not -o, but -f (I confuse them sometimes when not checking the CLI help) > should not ask to overwrite untouched files untouched...

Certain defaults through configure are now included: https://github.com/cakephp/bake/pull/365 Maybe a few more can help to remove the need for too much CLI typing for always the same args.

Can you make a PR against this repo? That would be easier to collaborate or give feedback.