The feedback about my last blog post about the GraphQL end-point in ASP.NET Core was amazing. That post was mentioned on reddit, many times shared on twitter, lInked on http://asp.net and - I'm pretty glad about that - it was mentioned in the ASP.NET Community Standup.

Because of that and because GraphQL is really awesome, I decided to make the GraphQL MiddleWare available as a NuGet package. I did some small improvements to make this MiddleWare more configurable and more easy to use in the Startup.cs

The master branch is the stable branch and I don't axcept PRs to that branch. To contribute, please create PRs based on the debelop branch. To play around with the latest changes, please also use the develop branch.

Changes on the develop branch ("next version" branch) will be pushed as preview releases to MyGet. To see whether this branch is stable, follow the builds on AppVeyor:

Changes on the master branch ("current version" branch) will be pushed as preview releases to NuGet. To see whether this branch is stable, follow the builds on AppVeyor:

Install that package via Package Manager Console:

PM> Install-Package GraphQl.AspNetCore -Pre

Install via dotnet CLI:

dotnet add package GraphQl.AspNetCore --version 1.0.0-preview1

You still need to configure your GraphQL schema using the graphql-dotnet library, as described in my last post.

First configure your schema(s) in the ConfigureServices method in Startup.cs. Make sure all referenced graph types are registered as well so they can be resolved from the container.

// Configure the default schema
services.AddGraphQl(schema =>
{
    schema.SetQueryType<BooksQuery>();
    schema.SetMutationType<BooksMutation>();
});

// Also register all graph types
services.AddSingleton<BooksQuery>();
services.AddSingleton<BooksMutation>();
services.AddSingleton<BookType>();
services.AddSingleton<AuthorType>();
services.AddSingleton<PublisherType>();

In the Configure method, you add the GraphQL middleware like this:

You can use two different ways to register the GraphQlMiddleware:

app.UseGraphQl("/graphql", new GraphQlMiddlewareOptions
{
    FormatOutput = true, // default
    ComplexityConfiguration = new ComplexityConfiguration()); //default
});

// or like this:

app.UseGraphQl("/graph-api", options =>
{
    options.SchemaName = "OtherSchema"; // only if additional schemas were registered in ConfigureServices
    //options.AuthorizationPolicy = "Authenticated"; // optional
});

Personally I prefer the second way, which is more readable in my opinion.

The GraphQlMiddlewareOptions are pretty simple.

• SchemaName: This specifies the registered schema name to use. Leave null for the default schema.
• AuthorizationPolicy: This configures the authorization policy name to apply to the GraphQL endpoint.
• FormatOutput: This property defines whether the output is prettified and indented for debugging purposes. The default is set to true.
• ComplexityConfiguration: This property is used to customize the complexity configuration.
• ExposeExceptions: This property controls whether exception details such as stack traces should be returned to clients. This defaults to false and should only be set to true in the Development environment.

This should be enough for the first time. If needed it is possible to expose the Newtonsoft.JSON settings, which are used in GraphQL library later on.

This library provides a middleware to add a GraphiQL UI to your GraphQL endpoint. To learn more about it and the way I created it, read the blog post about it: GraphiQL for ASP.NET Core

There's no NuGet Package available yet. I will provide one as soon as possible.

Open your Startup.cs and configure the middleware in the Configure method.

You can use two different ways to register the GraphiqlMiddleware:

app.UseGraphiql("/graphiql", new GraphQlMiddlewareOptions
{
    GraphQlEndpoint = "/graphql"
});


app.UseGraphiql("/graphiql", options =>
{
    options.GraphQlEndpoint = "/graphql";
});

Personally I prefer the second way, which is more readable in my opinion.

The GraphQlEndpoint needs to match the paht a GraphQL endpoint.

Currently the options just have two properties:

• GraphQlEndpoint: This is the path of your GraphQL end-point, configured with the GraphQlMiddleware. In theory it could be any possible path or URL that provides an GraphQL endpoint. Until now, I just tested it with the GraphQlMiddleware.

I would be happy, if you try this library and get me some feedback about it. A demo application to quickly start playing around with it, is available here on GitHub. Feel free to raise some issues and to create some PRs to improve this MiddleWare.