Code organization

How I should organize my code with this library? If my project have many queries and mutations, how to correctly split it? For example, ASP.NET uses MVC architecture and we can put code in different controllers and areas. I tried to create multiple QueryType, but seems this is not working. Only the last QueryType was created, and others were just skipped.

[michaelstaib]

Yes, I think this is a really good idea. We, will first focus on closing the last spec gaps with Version 0.4.0 and 0.5.0. After that we will focus on the configuration API.

I originally had three workflows in mind:

1. Schema-First

   Create your schema with the GraphQL syntax and than bind .net types to it.

2. Code-First

   Define your schema with csharp.

3. Mixed-Mode

   Merge schema-first and code-first with parts defined in the graphql syntax and other parts defined in csharp

But know I think we will allow for a 4th workflow where we flavour it like ASP.net. In this workflow you do not have to bother about the schema. You just create your controller like types and we will create from those a schema.

I will talk this through with my colleagues

[michaelstaib]

Also everything that you can do with the attributes now is available through the type api. you can also mix and match with these.