a2bea9b492
Fixes https://github.com/vercel/next.js/issues/16550 Add a graphql mutation operation in this example. The changes are: 1. Define mutation in schema `type-defs.graphqls` 2. Add mutation to `viewer.graphql ` that compiled to typescript code. 3. Add mutation resolver in `resolvers.ts` 4. [UI] add a input box and button to submit mutation request to change name. screenshot of change ![mutation_example](https://user-images.githubusercontent.com/1462027/91797123-5ffc4e00-ec54-11ea-910b-3ddb399b42f0.gif) |
||
---|---|---|
.. | ||
lib | ||
pages | ||
test | ||
.babelrc | ||
.gitignore | ||
.graphql-let.yml | ||
jest.config.js | ||
next-env.d.ts | ||
next.config.js | ||
package.json | ||
README.md | ||
tsconfig.json |
TypeScript and GraphQL Example
One of the strengths of GraphQL is enforcing data types on runtime. Further, TypeScript and GraphQL Code Generator (graphql-codegen) make it safer by typing data statically, so you can write truly type-protected code with rich IDE assists.
This template extends Apollo Server and Client Example by rewriting in TypeScript and integrating graphql-let, which runs TypeScript React Apollo in graphql-codegen under the hood. It enhances the typed GraphQL use as below:
import { useNewsQuery } from './news.graphql'
const News = () => {
// Typed already️⚡️
const { data: { news } } = useNewsQuery()
return <div>{news.map(...)}</div>
}
By default **/*.graphqls
is recognized as GraphQL schema and **/*.graphql
as GraphQL documents. If you prefer the other extensions, make sure the settings of the webpack loader in next.config.js
and .graphql-let.yml
are consistent.
Deploy your own
Deploy the example using Vercel:
How to use
Execute create-next-app
with npm or Yarn to bootstrap the example:
npx create-next-app --example with-typescript-graphql with-typescript-graphql-app
# or
yarn create next-app --example with-typescript-graphql with-typescript-graphql-app
Deploy it to the cloud with Vercel (Documentation).