Is type-graphql production trustworthy?

[kicks321]

We are looking to migrate our entire Graphql Stack over to type-graphql due to the feasibility behind writing resolvers.

Right now we use our own custom built ES6 classed based approach (similar to how controllers are built in REST).

Is type-graphql used in production by other clients, how long are we looking at solid support, and is there a multitude of contributions aside from the primary owner of this library?

[MichalLytek]

is there a multitude of contributions aside from the primary owner of this library?

I am a sole maintainer, but I see there's a bigger and bigger community around TypeGraphQL which propose new features and even open PRs with fixes.

TypeGraphQL is now a mature framework, that's why there's not too many commits recently as there's even no big bugs to fix.
V2.0 with GraphQL v16 support is incoming, then I plan to rewrite the internals to make it more modular, maintainable and extendable.

[guguji5]

hi @kicks321 , have you met the issue of Inheritance ?
#1407

[thiago-pinheiro]

Hello .. Good night. Yes, I already worked well with react inheritance and also next at mobiauto where I interned Em qui., 5 de jan. de 2023 às 00:12, Damon ***@***.***> escreveu:

…

hi @kicks321 <https://github.com/kicks321> , have you met the issue of Inheritance ? #1407 <#1407> — Reply to this email directly, view it on GitHub <#1377 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARYGRR7NWNJMHQOAPF6KIHLWQY325ANCNFSM6AAAAAAR4AD5II> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>