You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3fa03ec
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,7 @@
4
4
5
5
- A resolver can now be told what the engine will read off the objects it returns, so it can fetch only that instead of everything - the point of batching with `ResolveBulk` when the data comes from another database or service. Take an `IFieldSelection` parameter and the engine supplies it, the way it supplies `CancellationToken` and `QueryRequestContext`; new two-service `ResolveBulk`/`ResolveBulkAsync` overloads let a loader take it alongside its own service. It is not the caller's selection set: a selected field that is itself resolved from a service is replaced by the member its resolver reads, nested objects come through as paths (`Address.City`), `@skip`/`@include` are applied, fragments are expanded, aliases collapse, `__typename` is excluded, and one load is told the union of every place the field is selected. See [Fetching only the fields that will be used](https://entitygraphql.github.io/schema-creation/other-data-sources#fetching-only-the-fields-that-will-be-used).
6
6
- A field with a `ResolveBulk`/`ResolveBulkAsync` resolver that has to resolve per item instead of bulk loading now logs a warning to the `ILogger` the schema was built with, naming the field and why the bulk load could not run - the query shape usually controls it, so it is something a caller can act on. Turn it off with `ExecutionOptions.WarnOnBulkResolverFallback = false`. `ISchemaProvider.Logger` is new (exceptions keep going through `LogException`); it returns null by default so existing implementations are unaffected.
7
+
-`ToGraphQLSchemaString()` takes an optional `includeDescriptions` argument. Pass `false` to leave the `"""..."""` descriptions out of the generated SDL.
0 commit comments