Documentation around mutations

[markhepburn]

Hi, I've been doing a bit of investigation into graphql using your project and it's a great sweet-spot in usability thanks.

I was wondering though if there's an idiom for incorporating mutations as well?

From what I can tell the MethodResolver assumes that the ResolverContext.Source (ExecutionOptions.Root) is of the same type as the root query -- so if the schema has both a Query and a Mutation then they effectively have to be of the same type (unless you dynamically set Root in the options depending on the incoming query)?

I've worked around this by making the query methods static and injecting the data source (either through ResolveFieldContext or injectedParameters), but I was wondering if there was a better way.