Open
Description
Is there an existing issue that is already proposing this?
- I have searched the existing issues
Is your feature request related to a problem? Please describe it
I'm currently unsure how to extend schematics to include my own spin on how I create resources, so it would be great to help people like me out with an example of how to do so.
Describe the solution you'd like
Documentation on how to extend schematics, like @nestjs/schematics:resource.
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
I like to add MikroORM decorators to resources, use both resolvers and controllers at the same time, and other organization-specific code styles that would be nice to automate adding without having to rewrite and maintain everything.