Releases: asemio/otto-the-geek
Support .Preloaded() in Query and Mutation types
Prior to this release, when setting fields of the Query or Mutation types as .Preloaded()
, field resolution returned null due to a limitation in the underlying library. This release fixes that so that .Preloaded()
works properly everywhere.
Bugfix - refine ignoring via interface
1.0.5 fix ignore via interface
Bugfix: ignore props from base classes
This release fixes an issue where properties from base classes can't be ignored.
Disable parallel execution
This release disables the default of the underlying GraphQL-dotnet library which potentially runs queries in parallel. This is a dangerous default because:
- The default for EF Core is Scoped DbContexts, meaning that running with everything in a default configuration is invalid - EF Core DbContexts are not meant for concurrent access.
- Many cloud-based SQL offerings are very restrictive on the number of active connections. The number of connections that a single query might open becomes a function of the schema and the query.
To override this behavior, register graphql-dotnet's default DocumentExecuter
as IDocumentExecuter
:
services.AddSingleton<IDocumentExecuter, DocumentExecuter>();
Turn off metrics reporting by default
This release turns off apollo tracing which is apparently enabled by default. This will boost performance quite a bit.
Ready-to-go version with updated GraphQL under the hood
This release upgrades the underlying GraphQL (and related) dependencies. With that, we've went ahead and built against netcoreapp3.1
. There are various hacks and performance issues that we have abandoned as a part of this upgrade.
Upgrade to 3.2.0 of underlying GraphQL lib
1.0.0-alpha sanitize version numbers for alpha releases
Handle descriptions for enum values
Merge pull request #32 from asemio/enum-desc handle enum description attribute
Add asynchronous authorization
You can now authorize fields asynchronously.
Bugfix - Custom Scalar Types
The underlying GraphQL library we're using has a poorly-designed API around custom scalar graph types. We found a bug with our custom graph type logic; this release fixes that bug. See #26 for details.