Prefer SubFields vs. SelectionSet

Looks like a pretty cool library!

Not sure if it is well known, but the ResolveFieldContext does have a SubFields property which is the fields that should be requested. It looks like that Dapper.GraphQL may have a bug in that even though a field is in the SelectionSet, it may not necessarily be allowed to be returned (due to directives mainly).

[benmccallum]

Hey @joemcbride, I’m currently re-visiting this TODO and wondering… is it possible now to get the SubFields of the SubFields yet? Doesn’t look like it as Field doesn’t have a SubFields prop yet. Should I create an issue in the GraphQL repo, or is this just flat out impossible?

If I just use SelectionSet, it seems like it still only gives you what was asked in the query, so are you saying that directives are the only graphql feature that should would make SubFields and SelectionSet different? Or are there other cases?

[benmccallum]

Another note for this change @dougrday , looks like when you upgrade to a later version of GraphQL that GraphQL.Type.Schema.ResolveType has been deprecated in favour of using the DependencyResolver property which is no longer a func but a concrete type implementing GraphQL.IDependencyResolver, so the docs/example will need to update similarly.

@joemcbride, is there a default one configured for asp.net core servicesCollection or do we just need to set the DependencyResolver to a barebones class that calls asp.net core’s serviceProvider anyway?