Shane Krueger

See: - #993 This 'resolves' the issue noticed by @triumphtang and @yuchen-w in #993 at the cost of returning Forbidden instead of Unauthorized for typical implementations when policy/role requirements are...

Refactoring for adding/fixing these issues: - By inheriting from GraphQLHttpMiddleware, requests now honor all of these options which were not supported previously: - AuthenticationSchemes - AuthorizedPolicy - AuthorizedRoles - AuthorizationRequired...

`HttpClient.Timeout` defaults to a 100 second timeout. I have a reproducible problem where this timeout period is not long enough for Kraken to finish processing the request. It could be...

Review if connection builders are provided and/or how they interact or conflict with the connection builders provided with the main GraphQL.NET library

- e.g. dataloaders or authentication.

Code seems designed for in-memory databases. Need to consider how it would be used in a typical scenario (with a backing database/repository) versus only for in-memory databases

- e.g. `MutationInputs` is identical to `Inputs`