docs: directive(s) not present in typeDefs when using buildTypeDefsAndResolvers(Sync)

[carlocorradini]

I think we should add to the docs that buildTypeDefsAndResolvers and buildTypeDefsAndResolversSync do not have any directive(s) in typeDefs.

[MichalLytek]

We could even replace the printSchema with the function from graphql tools to have directives printed.

[carlocorradini]

Therefore, add graph-tools as a dependency?
This could solve all directive(s) issues :)

[MichalLytek]

Yes, until we have a plugin system and modular packages, we need to download everything even if not needed for most of the users 🤔

[carlocorradini]

Any idea for the implementation of a plugin/extension system?

[MichalLytek]

Started 2 years ago a complete rewrite from scratch 😅

[carlocorradini]

Yup, saw it!
All the ideas are implemented in v2? Or you simply added them as idea in GitHub project?

[MichalLytek]

The board was up to date with the state of my local branch. Now I think I would need to update lerna to nx, npm workspaces, etc. 😄

[carlocorradini]

If I can help, I love TypeGraphQL and I'm using it in my Master's Thesis (and a lot of other projects too), so... yeah, TypeGraphQL all the way 😂

Several months ago I may have agreed with you  for ditching Lerna with something else but now Lerna is super carried and heavily maintained.
Do you want to use Lerna for packages (i.e., plugins, TypeGraphQL ecosystem), I've also used npm workspaces, and please let me know if I can assist... 

[carlocorradini]

Moreover, I think that could be super useful if we create a TypeGraphQL chatroom (i.e., Discord, Slack, etc.) for thoughts, etc.