Hi, I’m not sure which question I should answer here so I’ll go with: “Why not routes are generated when we generate a model in a plugin”
The answer is that a plugin model doesn’t get a core controller and a core service instance linked to it because we don’t want to create code that a plugin developer don’t want nor add unwanted routes. So by default a model in a plugin is just a model and you add your APIs manually. In the future we might offer a quick way to generate a CRUD API for a model programmatically but this will need some greater changes first.
In v4 the plugin loading will change from a file loading to a plain export from the developper. This means you will be able to organise your code however you want.