Minor release, upgraded references (Irony, System.Text.Json), fixed unit tests.
- Subscriptions, full implementation based on SignalR - see SubscriptionTests.cs in HttpTests project.
- Added GraphQLClient.OnError event
- Server automatically returns the response header with time it took processing the request, ex: "X-GraphQL-Server-Statistics: exec-time=5.6ms". Useful when you want to quickly see on the client (web browser) - why it took so long? (or quick!)
- Added IResolverClassAsync interface, async version of IResolverClass, to allow resolver instances to initialize in async manner.
- Added IRequestContext.HostServices property (IServiceProvider) - this is service provider passed from the host AspNetCore app, you can use it in resolver to reach any registered service.
- Added flag ThrowOnError to automatically throw ClientGraphQLError if server returns errors in response. This does not apply to subscriptions (push messages).
- New option GraphQLServerOptions.IgnoreOutNullFaults - (default is set). On the server, when the resulting value for a non-nullable field is null (returned by resolver), the server normally throws an error and report the error to client. That's expected, violation of the contract and server acknoledges this. But this gets very annoying and troublesome in some situations, when you work with external data sources, or even externally defined types (which you use in your GraphQL model). So if you set this flag, the server would ignore the fault and return null as the field value.
- Similar flag GraphQLServerOptions.RefTypesNullableByDefault - make all fields of reference types (string, objects, etc) nullable by default. To make it NonNull, use [NonNull] attribute. Useful when you use externally defined types in your GraphQL model, and have no control over type definitions and cannot put [Null] attribute on the fields.
- Switched Json serialization to System.Text.Json package (from good old NewtonSoft). Support for dynamic return types (keyword dynamic) in GraphQLClient is dropped since this new serializer does not support it (fully).
- Upgraded dependent package references. Microsoft changed the distribution model for AspNetCore (no longer in packages but in one App bundle), so I could not find a way for the package NGraphQL.Server.AspNetCore to stay at .NET Standard. Now this package/assembly is double-targeted to Net6 and Net8. The rest of the packages are still on .NET Standard 2.0
- Added extension methods for GraphQL server setup, so now you can configure the server using a typical pattern; the code is shorter:
builder.AddGraphQLServer(graphQLServer);
...
app.MapGraphQLEndpoint(); The default GraphQLController that handles GraphQL requests is provided with the NGraphQL.Server.AspNetCore package and is configured with the methods shown above.
- Name changes: GraphQLHttpServer -> GraphQLHttpHandler; ServerResponse -> GraphQLResult
- Fixed a minor bug in introspection queries, now introspection types/fields themselves are not returned in introspection queries. The clients like Graphiql and Altair were complaining about this.
- Removed dependency on Graphiql package to display GraphQL visual tool. Now the test app (Things.GraphQL.HttpServer project) opens the page of Chrome Altair extension. Make sure you install it in Chrome before launching the app.
Implementation of long-asked feature in GraphQL - allow Input types to be used as (output) Object types. So you can use Input type as field type in Object types, including methods return types. But still, Object types may not be used in Input types. Essentially Input types are now treated as restricted Object types, Input types are subset of Object types.
There are often situations when you have a simple data object, and you want to use it in both directions - as server input and output of fields and methods. But you can't - there's this strange restriction in the current GraphQL spec. You end up defining two identical types, one for input, one for output. NGraphQL now drops this restriction. It DOES NOT break any compatibility, it is non-breaking extension. If you don't like it - just don't use it.
There are also a few minor fixes in this release, a bit of refactoring in unit tests.
A minor release with small fixes, dependencies upgrades
- Upgraded all 'apps' to Net6 (from Core 3.1 which is oudated). All nuget packages/libs remain at .Net Standard 2.0, for most compatibility.
- Upgraded Newtonsoft.Json lib to 13.0.1 (required for discovered vulnerability in previous versions)
- Small refactorings, few serialization/deserialization fixes.
A number of features to reach formal compliance with GraphQL Specification, 2021 version.
- Allow interfaces implement other interfaces
- Implementation of an interface (Object type or another interface) can have covariant field types - not necessarily exactly matching, but 'sub-classed'. Improvement in NGraphQL: c# does not allow covariant implementation of interfaces, so you cannot use c# inheritance to express this GraphQL relationship. Now you can use ImplementsAttribute on implementor type to point to another interface that is implemented in 'covariant' manner.
- Fields results merging for complex fields
- SpecifiedBy(url) attribute and introspection field for custom scalars.
- Repeatable directives and repeatable keyword in SDL files
- Allowing directives on variable definitions
Map Scalar type (Dictionary<string, object>)
Minor bug fix - allow very large number literals for decimal values
Internal refactoring and bug fixes:
- mapping entities to multiple GraphQL types;
- new infrastructure for supporting standard and custom directives
- improved integration with VITA ORM, added RequestContext.VitaOperationContext field; set by VitaWebMiddleWare if configured in ASP.NET Core server. Improves integration with VITA authentication
- Added option to suppress parallel execution - strongly recommended option for database-connected applications
- multiple bug fixes
Patch, bug fix for issue: incorrect handling mapping expressions when field expression returns GraphQL type directly.
Mostly internal cleanup and refactoring. Some changes are part of an effort to integrate with DB-connected apps. A sample "GraphQL-over-database" project is published as part of VITA ORM repo.
Server and client components, samples, GraphiQL integration.