Add the option to generate schema types from TS classes

[vnenkpet]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

What is the motivation / use case for changing the behavior?

The current implementation forces us to have a GraphQL types defined in a .graphql file. I suggest taking inspiration from the https://19majkel94.github.io/type-graphql/ library and add the option to completely throw away any external schema input and allow us to generate the schema from the classes with decorators (https://19majkel94.github.io/type-graphql/docs/types-and-fields.html) similar to how Resolvers are already handled. A lot of the API of the type-graphql library seems compatible with nestjs/graphql already in principle. It just generally seems like a better fit for how Nest is structured the current solution IMO. I worked with type-graphql before and it works great, but it lacks the overall architecture of nestjs so it'd be nice if nestjs could incorporate some or all of its features.

Environment

Nest version: 5.5.0

 
For Tooling issues:
- Node version: irrelevant
- Platform: irrelevant

Others:

[kamilmysliwiec]

See #85. I'm working on it already

[vnenkpet]

Oh I'm an idiot. I opened that exact issue in a separate tab to check if it's not what I'm proposing and forgot to read it before writing this :) But great! Thanks.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.