refactor: migrate make:scaffold as modern command

[paulbalandan]

Description
Follow up to #10524 . This is the last framework command to be migrated into the modern command API.

A behavioral improvement over legacy: a missing class name will now be asked once instead of one per component.

This is currently branched from the make:migration PR and will be rebased once it merges.

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value (without duplication)
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[michalsn]

Awesome.

[michalsn]

Bottom line - I was thinking about adding a crud command to generate a full CRUD skeleton using plain HTML, without any styling. Of course, it could also support a custom "template" so the view layer could be adjusted as needed.

I probably won't have time to work on this in September, but I'm wondering whether this will now be possible, or whether things have become more complicated.

[paulbalandan]

Do you mean something like a GUI?

[michalsn]

In a way, yes. We already have scaffold, which only generates the basic files without any actual implementation.

The idea behind crud would be to generate a controller, model/entity, views, routes, etc, that work out of the box.

[paulbalandan]

Ah yes. The modern command API will make it easier. It has added a lot of improvements over the legacy API, including composition of several commands. Some questions in mind are where would the data come from (from passed options I suppose) and should routes be added directly or just print and let the dev copy paste it.

[michalsn]

Okay, that's encouraging.

Yes, data would come from input, like make:crud Post --fields=title:string,body:text. I suppose we can start by printing out routes, although I wonder if 4.8 is not the right moment to move toward auto-routes (improved) being the default option for the framework.

[paulbalandan]

On flipping to auto improved, I'd defer this to an issue for its own discussion. For one it would need to update the Routes file and there is I believe an open issue for the mode's extensibility.

For crud itself, I'd suggest we keep the current way so that the generated files would work out of the box. Then, add an option for auto routes if needed, which would update the generated controller's method names.

[michalsn]

Oh... yes, changing routes would be a totally different PR. I was just thinking out loud.