hiro/apollo-server
1
0
Fork 0
mirror of https://github.com/vale981/apollo-server synced 2025-03-06 10:11:40 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Minor edits to the migration guide

Browse source
This commit is contained in:
Peggy Rayzis 2018-05-03 11:53:52 -07:00
parent 990e741068
commit ca008e806e
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/source/migration-two-dot.md
View file

@ -3,7 +3,7 @@ title: Migrating to v2.0 Beta
description: How to migrate to Apollo Server 2.0 beta
---
Migrating from Apollo Server 1 to Apollo Server 2.0 beta is a walk in the park.
The Apollo Server 2.0 beta dramatically simplifies the API for building a GraphQL server without compromising on features. It's also completely backward compatible, so you don't have to worry about breaking changes when upgrading. We do recommend upgrading to the new API as soon as possible to take advantage of all the latest Apollo Server features. To learn how to migrate to the 2.0 beta from version 1.0, please read the following guide.
### Node.js
@ -17,7 +17,7 @@ Once updated, your existing code should work as intended. No errors!
### The `gql` tag
Apollo Server 2.0 ships with the `gql` tag. You don't need to require `graphl-tags` anymore. It's not necessary to use the `gql` tag on the server. However, we recommend it for editor syntax highlighting and also to enable future functionality including statically analyzing GraphQL queries.
Apollo Server 2.0 ships with the `gql` tag for editor syntax highlighting and auto-formatting with Prettier. In the future, we will be using it for statically analyzing GraphQL queries, so we recommend wrapping your schema with `gql` today. Unlike the `gql` tag on the client, it does not parse the query string into an AST.
```js
const { ApolloServer, gql } = require('apollo-server');