FSharp.HotChocolate 0.1.3

FSharp.HotChocolate

Support for F# types and nullability in HotChocolate.

Quick start

1. Remove any existing calls to AddFSharpTypeConverters or AddTypeConverter<OptionTypeConverter>.
2. Call AddFSharpSupport:

   .AddGraphQLServer().AddFSharpSupport()
   

Features

Idiomatic F# nullability through Option<_>

All fields defined in F# (including HotChocolate type extensions for types not defined in F#) will have idiomatic F# nullability applied. This means that everything except Option-wrapped values will be non-nullable (!) in the GraphQL schema. Any usages of [<GraphQLNonNullType>], or NonNullType<_> in [<GraphQLType>], will be ignored.

Opting out of F# nullability

Due to limitations (see below) or other reasons, you may want to opt out of F# nullability for a certain scope. You can apply the SkipFSharpNullability attribute to parameters, members, types (including HotChocolate type extensions), or whole assemblies to disable F# nullability processing for that scope.

Limitations in F# nullability

• When using global object identification, Option-wrapped node resolvers are not supported (#5).
• When using global object identification, Option-wrapped ID values inside lists are not supported (#6).
• Support for ValueOption<_> is not yet added (#10).
• When using UsePaging, the nullability of the first, last, before, and after parameters is controlled by HotChocolate. These are always nullable. Therefore, if these parameters are explicitly present in your method (e.g. if doing custom pagination), make sure you wrap them in Option<_>. The only exception is if you use RequirePagingBoundaries = true with AllowBackwardPagination = false; in that case, HotChocolate will effectively enforce that these (only) two parameters are non-null on input (even though they are nullable in the schema), and it's safe to not wrap them in Option<_> in code.

Async<_> fields

Fields can now be Async<_>.

The computations are automatically wired up to the RequestAborted cancellation token. If you do not want that, please convert the Async<_> to Task<_> yourself as you see fit.

Limitations in Async<_> fields

• When using some built-in middleware such as [<UsePaging>], Async<_> is not supported for that field. (#8).
• When using global object identification, Async<_> is not supported for node resolvers (#9).

Acknowledgements

Many thanks to @Stock44 for creating this gist that sparked this project. Without that, I'd have no idea where to even begin.

Deployment checklist

For maintainers.

• Make necessary changes to the code
• Update the changelog
• Update the version and release notes in the fsproj files
• Commit and tag the commit in the format v/x.y.z (this is what triggers deployment)
• Push the changes and the tag to the repo. If the build succeeds, the package is automatically published to NuGet.