apollo-server/docs/source/api/apollo-server.md
2018-04-26 22:37:14 +03:00

4.6 KiB

title
apollo-server

This API reference documents the exports from the apollo-server, and apollo-server/{variant} packages (e.g. apollo-server/express). Both the root module and the module sub-paths export the same functionality.

ApolloServer

The ApolloServer class is used to create an instance of Apollo Server. An instance of Apollo Server will only be available when listen is called.

If using Apollo Server as middleware in an existing project, it is also necessary to call applyMiddleware.

new ApolloServer(options): <ApolloServer>

Parameters

  • options: <Object>
    • typeDefs: <String inside gql tag> (required)

      This is a string representation of your GraphQL Schema Definition Language (SDL).

    • resolvers: <Object> (required)

      Type: Object

      This should be a map of resolvers for the types defined in typeDefs. The key should be the type name and the value should be a Function to be executed for that type.

Returns

ApolloServer

ApolloServer.prototype.listen(options): Promise

Parameters

  • options: <Object>

    The options supports all Node.js

    • port: <String> | <Number>
    • path: <String>
    • backlog: <Number>
    • exclusive: <Boolean>

    // engine launcher options engineLauncherOptions?: EngineLauncherOptions; // WebSocket options keepAlive?: number; onConnect?: ( connectionParams: Object, websocket: WebSocket, context: ConnectionContext, ) => any; onDisconnect?: (websocket: WebSocket, context: ConnectionContext) => any;

Returns

Type Promise

ApolloServer.prototype.applyMiddleware(app, options): Promise

  • app: <HttpServer> (Required)

  • options: <Object>

    • path: <String>

      Default: /

      The path which the middleware will be mounted on.

    • subscriptions: <Boolean>

      Default: false

      When set to true, WebSockets will be enabled to allow for subscription support.

gql

The gql is a template literal tag. Template literal tags exist to provide special functionality for what would otherwise be a template literal. Template literals were introduced in recent versions of ECMAScript to provide embedded expressions (i.e. `A string with interpolated ${variables}`.)

In the case of GraphQL, the gql tag is used to surround GraphQL operation and schema language (which are represented as Strings), and makes it easier to differentiate from ordinary strings. This is particularly useful when performing static analysis on GraphQL language (e.g. to enable syntax highlighting, code generation, etc.) and avoids need for tools to "guess" if a string contains GraphQL language.

Usage

Place graphQL schema definitions (SDL), queries or other operations into the gql template literal tag. Keep in mind that template literals use the grave accent (`) and not normal quotation marks (e.g. not " or '):

const typeDefs = gql`
  type Author {
    name
  }
`;

makeExecutableSchema

addMockFunctionsToSchema(options)

The addMockFunctionsToSchema method is re-exported from apollo-server as a convenience.

Given an instance of a GraphQLSchema and a mock object, modifies the schema (in place) to return mock data for any valid query that is sent to the server.

If preserveResolvers is set to true, existing resolve functions will not be overwritten to provide mock data. This can be used to mock some parts of the server and not others.

Parameters

  • options: <Object>
    • schema: <GraphQLSchema> (required)

      Pass an executable schema (GraphQLSchema) to be mocked.

    • mocks: <Object>

      Should be a map of types to mock resolver functions, e.g.:

      {
        Type: () => true,
      }
      

      When mocks is not defined, the default scalar types (e.g. Int, Float, String, etc.) will be mocked.

    • preserveResolvers: <Boolean>

      When true, resolvers which were already defined will not be over-written with the mock resolver functions specified with mocks.

Usage

const { addMockFunctionsToSchema } = require('apollo-server');

// We'll make an assumption that an executable schema
// is already available from the `./schema` file.
const executableSchema = require('./schema');

addMockFunctionsToSchema({
  schema: executableSchema,
  mocks: {
    // Mocks the `Int` scalar type to always return `12345`.
    Int: () => 12345,

    // Mocks the `Movies` type to always return 'Titanic'.
    Movies: () => 'Titanic',
  },
  preserveResolvers: false,
});