[example with-typescript-graphql] Fix type error (vercel#10269)

piglovesyou · Luis Alvarez D · commit f13bf1e2bfd7 · 2020-01-25T22:32:58.000-05:00
* fix: Type error

* Improve README.md
diff --git a/examples/with-typescript-graphql/README.md b/examples/with-typescript-graphql/README.md
@@ -1,11 +1,11 @@
-# GraphQL and TypeScript Example
+# TypeScript and GraphQL Example
 
 One of the strengths of GraphQL is [enforcing data types on runtime](https://graphql.github.io/graphql-spec/June2018/#sec-Value-Completion). Further, TypeScript and [GraphQL Code Generator](https://graphql-code-generator.com/) (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](https://github.com/zeit/next.js/tree/canary/examples/api-routes-apollo-server-and-client#readme) by rewriting in TypeScript and integrating [graphql-let](https://github.com/piglovesyou/graphql-let#readme), which runs [TypeScript React Apollo](https://graphql-code-generator.com/docs/plugins/typescript-react-apollo) in [graphql-codegen](https://github.com/dotansimha/graphql-code-generator#readme) under the hood. It enhances the typed GraphQL use as below.
 
 ```typescript jsx
-import { useNewsQuery } from './news.grpahql'
+import { useNewsQuery } from './news.graphql'
 
 const  News: React.FC = () => {
 	// Typed already️⚡️
@@ -59,7 +59,7 @@ now
 
 ## Notes
 
-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` point to the same files.
+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.
 
 Note: Do not be alarmed that you see two renders being executed. Apollo recursively traverses the React render tree looking for Apollo query components. When it has done that, it fetches all these queries and then passes the result to a cache. This cache is then used to render the data on the server side (another React render).
 https://www.apollographql.com/docs/react/api/react-ssr/#getdatafromtree
diff --git a/examples/with-typescript-graphql/lib/resolvers.ts b/examples/with-typescript-graphql/lib/resolvers.ts
@@ -1,4 +1,6 @@
-const resolvers = {
+import { IResolvers } from 'apollo-server-micro'
+
+const resolvers: IResolvers = {
   Query: {
     viewer(_parent, _args, _context, _info) {
       return { id: 1, name: 'John Smith', status: 'cached' }
