Skip to content

Releases: apollographql/apollo-server

@apollo/[email protected]

24 Aug 19:18
e8c00a7
Compare
Choose a tag to compare

Patch Changes

  • #7699 62e7d940d Thanks @trevor-scheer! - Fix error path attachment for list items

    Previously, when errors occurred while resolving a list item, the trace builder would fail to place the error at the correct path and just default to the root node with a warning message:

    Could not find node with path x.y.1, defaulting to put errors on root node.

    This change places these errors at their correct paths and removes the log.

@apollo/[email protected]

24 Aug 19:18
e8c00a7
Compare
Choose a tag to compare

Patch Changes

@apollo/[email protected]

04 Aug 19:58
a48e8e0
Compare
Choose a tag to compare

Patch Changes

@apollo/[email protected]

04 Aug 19:58
a48e8e0
Compare
Choose a tag to compare

Patch Changes

@apollo/[email protected]

27 Jul 19:50
1235611
Compare
Choose a tag to compare

Minor Changes

  • #7617 4ff81ca50 Thanks @trevor-scheer! - Introduce new ApolloServerPluginSubscriptionCallback plugin. This plugin implements the subscription callback protocol which is used by Apollo Router. This feature implements subscriptions over HTTP via a callback URL which Apollo Router registers with Apollo Server. This feature is currently in preview and is subject to change.

    You can enable callback subscriptions like so:

    import { ApolloServerPluginSubscriptionCallback } from '@apollo/server/plugin/subscriptionCallback';
    import { ApolloServer } from '@apollo/server';
    
    const server = new ApolloServer({
      // ...
      plugins: [ApolloServerPluginSubscriptionCallback()],
    });

    Note that there is currently no tracing or metrics mechanism in place for callback subscriptions. Additionally, this plugin "intercepts" callback subscription requests and bypasses some of Apollo Server's internals. The result of this is that certain plugin hooks (notably executionDidStart and willResolveField) will not be called when handling callback subscription requests or when sending subscription events.

    For more information on the subscription callback protocol, visit the docs:
    https://www.apollographql.com/docs/router/executing-operations/subscription-callback-protocol/

Patch Changes

@apollo/[email protected]

27 Jul 19:50
1235611
Compare
Choose a tag to compare

Patch Changes

@apollo/[email protected]

22 Jul 01:12
5ccecb0
Compare
Choose a tag to compare

Patch Changes

@apollo/[email protected]

22 Jul 01:12
5ccecb0
Compare
Choose a tag to compare

Patch Changes

@apollo/[email protected]

21 Jul 00:49
9139a28
Compare
Choose a tag to compare

Minor Changes

  • #7634 f8a8ea08f Thanks @dfperry5! - Updating the ApolloServer constructor to take in a stringifyResult function that will allow a consumer to pass in a function that formats the result of an http query.

    Usage:

    const server = new ApolloServer({
      typeDefs,
      resolvers,
      stringifyResult: (value: FormattedExecutionResult) => {
        return JSON.stringify(value, null, 2);
      },
    });

@apollo/[email protected]

21 Jul 00:49
9139a28
Compare
Choose a tag to compare

Patch Changes