Tweak the name of the config used to enable @defer in the QP

query-planner-js/src/__tests__/buildPlan.defer.test.ts

@@ -4,7 +4,7 @@ import { QueryPlanner } from '@apollo/query-planner';
 import { composeAndCreatePlanner, composeAndCreatePlannerWithOptions } from "./buildPlan.test";
 
 function composeAndCreatePlannerWithDefer(...services: ServiceDefinition[]): [Schema, QueryPlanner] {
-  return composeAndCreatePlannerWithOptions(services, { deferStreamSupport: { enableDefer : true }});
+  return composeAndCreatePlannerWithOptions(services, { incrementalDelivery: { enableDefer : true }});
 }
 
 describe('handles simple @defer', () => {

query-planner-js/src/buildPlan.ts

@@ -1911,7 +1911,7 @@ export function computeQueryPlan({
   let assignedDeferLabels: Set<string> | undefined = undefined;
   let hasDefers: boolean = false;
   let deferConditions: SetMultiMap<string, string> | undefined = undefined;
-  if (config.deferStreamSupport.enableDefer) {
+  if (config.incrementalDelivery.enableDefer) {
     ({ operation, hasDefers, assignedDeferLabels, deferConditions } = operation.withNormalizedDefer());
   } else {
     // If defer is not enabled, we remove all @defer from the query. This feels cleaner do this once here than

query-planner-js/src/config.ts

@@ -23,7 +23,7 @@ export type QueryPlannerConfig = {
   // new `passthroughSubgraphs` option that is the list of subgraph to which we can pass-through some @defer
   // (and it would be empty by default). Similarly, once we support @stream, grouping the options here will
   // make sense too.
-  deferStreamSupport?: {
+  incrementalDelivery?: {
     /**
      * Enables @defer support by the query planner.
      *
@@ -41,7 +41,7 @@ export function enforceQueryPlannerConfigDefaults(
   return {
     exposeDocumentNodeInFetchNode: true,
     reuseQueryFragments: true,
-    deferStreamSupport: {
+    incrementalDelivery: {
       enableDefer: false,
     },
     ...config,