GraphQLdotNet Best/Better Practices?

I’m involved in a project that has a single GraphQLObjectType for queries and one for Mutations. This has resulted in a massive pile of garbage, organizationally speaking. I’m wondering what patterns others have used to organize their queries and mutations in larger projects. The GraphQLdotNet examples aren’t very involved, so they haven’t helped in this regard.

Thank you in advance!

submitted by /u/reddevit
[link] [comments]

Leave a Reply