metaforecast/docs/graphql.md

Metaforecast website is implemented on top of GraphQL API.

Tech stack:

• Pothos on the backend for implementing our graphql server
• urql on the frontend
• GraphQL Code Generator for schema generation, queries generation and schema introspection

Rationale for this stack can be found on #32 and #21 in comments.

Code layout

List of all files used for graphql:

• schema.graphql, GraphQL schema generated by graphql-code-generator.
• codegen.yml, graphql-code-generator config
• graphql.config.yaml, GraphQL Config for better VS Code integration (VS Code GraphQL extension type-checks graphql files thanks to it)
• src/pages/api/graphql.ts implements the GraphQL HTTP endpoint and GraphQL playground
• src/web/urql.ts contains some helper functions.

src/graphql/ dir contains GraphQL server code.

*.graphql files in src/web/** contain GraphQL fragments, queries and mutations which are used on the frontend.

graphql-code-generator converts those into *.generated.ts files which can be imported from the React components.

Recipes

I want to check out what Metaforecast's GraphQL API is capable of

Go to /api/graphql and do some queries by hand. Note the "Docs" link in the top right corner.

I want to add a new query/mutation to our schema

Read the Pothos docs to learn how to implement new objects and fields. Add the new code somewhere in src/graphql/schema/.

I want to display a new piece of data on the metaforecast website

• add a query in a nearest queries.graphql file (if there isn't one, create it)
• run gql-gen (or keep it running with gql-gen -w) to get a graphql.generated.ts file
• use useQuery with your new MyQueryDocument which you can import from the graphql.generated.ts file

If you need SSR, you'll also need to do the same query with the same variables from your page's getServerSideProps function. Check out any existing page which calls ssrUrql.

(You might not need to use useQuery in your components if you're doing SSR and the page content is not dynamic, just pass the data from getServerSideProps in props and avoid GraphQL on the client side).