@apollo/server-integration-testsuite@4.0.0-alpha.10

Patch Changes

• #6857 15b1cb2e9 Thanks @glasser! - Errors thrown in resolvers and context functions can use extensions.http to affect the response status code and headers. The default behavior when a context function throws is now to always use status code 500 rather than comparing extensions.code to INTERNAL_SERVER_ERROR.

• Updated dependencies [15b1cb2e9]:

  • @apollo/server@4.0.0-alpha.10

@apollo/server@4.0.0-alpha.9

Patch Changes

• #6855 3e4ab3fca Thanks @glasser! - New usage reporting option sendTraces: false to only send usage reports as aggregated statistics, not per-request traces.

• #6855 3e4ab3fca Thanks @glasser! - Remove Apollo-internal internal_includeTracesContributingToStats. This should not have been used other than inside Apollo's own servers.

• #6855 3e4ab3fca Thanks @glasser! - The usage reporting option debugPrintReports now displays reports via logger.info rather than logger.warn.

• #6855 3e4ab3fca Thanks @glasser! - Rename usage reporting option sendErrorsInTraces (added in 4.0.0-alpha.4) to sendErrors, as it also affects error statistics outside of traces.

@apollo/server-integration-testsuite@4.0.0-alpha.9

Patch Changes

• #6855 3e4ab3fca Thanks @glasser! - Rename usage reporting option sendErrorsInTraces (added in 4.0.0-alpha.4) to sendErrors, as it also affects error statistics outside of traces.

• Updated dependencies [3e4ab3fca, 3e4ab3fca, 3e4ab3fca, 3e4ab3fca]:

  • @apollo/server@4.0.0-alpha.9

@apollo/server@4.0.0-alpha.8

Patch Changes

• #6841 3320fee92 Thanks @glasser! - Upgrade @apollo/server-gateway-interface to have laxer definition of overallCachePolicy.

• #6731 9fc23f799 Thanks @trevor-scheer! - Use extensions for all imports to accommodate TS users using moduleResolution: "nodenext"

• #6846 2cab8f785 Thanks @trevor-scheer! - Ensure executionDidEnd hooks are only called once (when they throw)

@apollo/server-integration-testsuite@4.0.0-alpha.8

Patch Changes

• Updated dependencies [3320fee92, 9fc23f799, 2cab8f785]:
  • @apollo/server@4.0.0-alpha.8

@apollo/server@4.0.0-alpha.7

Patch Changes

• #6817 eca003fdc Thanks @glasser! - Move ApolloServerPluginGraphQLPlayground into its own package.

@apollo/server-plugin-landing-page-graphql-playground@4.0.0-alpha.0

Major Changes

• #6817 eca003fdc Thanks @glasser! - Move ApolloServerPluginGraphQLPlayground into its own package.

Patch Changes

• Updated dependencies [eca003fdc]:
  • @apollo/server@4.0.0-alpha.7

@apollo/server-integration-testsuite@4.0.0-alpha.7

Patch Changes

• #6817 eca003fdc Thanks @glasser! - Move ApolloServerPluginGraphQLPlayground into its own package.

• Updated dependencies [eca003fdc]:

  • @apollo/server-plugin-landing-page-graphql-playground@4.0.0-alpha.0
  • @apollo/server@4.0.0-alpha.7

@apollo/server@4.0.0-alpha.6

Patch Changes

• #6814 cf0fcf49a Thanks @glasser! - Several changes relating to plugins:

  • Remove the server field on GraphQLRequestContext and GraphQLServerContext (ie, the arguments to most plugin hook methods). This was added during AS4 development and did not exist in AS3.

  • Add logger and cache fields to GraphQLRequestContext and GraphQLServerContext. The logger fields and GraphQLRequestContext.cache existed in AS3 and had been previously removed for redundancy with the server field. (Unlike in AS3, logger is readonly.)

  • ApolloServerPlugin is now declared as <in TContext extends BaseContext = BaseContext> rather than <in out TContext>. This means that you can declare a plugin that doesn't care about contextValue to simply implement ApolloServerPlugin and it will work with any ApolloServer<NoMatterWhatContext>. This should make it easy to write plugins that don't care about context.

  • Remove the ability to specify a factory function as an element of the plugins list in the ApolloServer constructor. (Reducing the number of ways to specify constructor options helps keep type errors simpler.) As far as we know the main use case for this (referring to the ApolloServer itself when creating the plugin) can be handled with the new-in-AS4 ApolloServer.addPlugin method.

@apollo/server-plugin-response-cache@4.0.0-alpha.4

Patch Changes

• #6814 cf0fcf49a Thanks @glasser! - Several changes relating to plugins:

  • Remove the server field on GraphQLRequestContext and GraphQLServerContext (ie, the arguments to most plugin hook methods). This was added during AS4 development and did not exist in AS3.

  • Add logger and cache fields to GraphQLRequestContext and GraphQLServerContext. The logger fields and GraphQLRequestContext.cache existed in AS3 and had been previously removed for redundancy with the server field. (Unlike in AS3, logger is readonly.)

  • ApolloServerPlugin is now declared as <in TContext extends BaseContext = BaseContext> rather than <in out TContext>. This means that you can declare a plugin that doesn't care about contextValue to simply implement ApolloServerPlugin and it will work with any ApolloServer<NoMatterWhatContext>. This should make it easy to write plugins that don't care about context.

  • Remove the ability to specify a factory function as an element of the plugins list in the ApolloServer constructor. (Reducing the number of ways to specify constructor options helps keep type errors simpler.) As far as we know the main use case for this (referring to the ApolloServer itself when creating the plugin) can be handled with the new-in-AS4 ApolloServer.addPlugin method.

• Updated dependencies [cf0fcf49a]:

  • @apollo/server@4.0.0-alpha.6