You’re comparing apples to oranges. Yes, at a high level both redux and apollo-client provide a way for you to manage global application state. However, redux allows you to create a predictable state container that changes in response to the actions you define. That means redux offers: Predictability. Reducers are pure functions — given the … Read more
Please replace your expressGraphQL with graphqlHTTP as it was destructured Use: const { graphqlHTTP } = require(‘express-graphql’); or const expressGraphQL = require(‘express-graphql’).graphqlHTTP This is because a method called graphqlHTTP exist in the express-graphql module and you are destructure with another method name that does not exist in the module I also noticed that you have … Read more
GraphQL relies on both the server and the client knowing ahead of time what fields are available available for each type. In some cases, the client can discover those fields (via introspection), but for the server, they always need to be known ahead of time. So to somehow dynamically generate those fields based on the … Read more
You have to add id also to the creator field: query getEvent($eventId: ID!) { Event(id:$eventId) { id headline photo location startTime creator { id username photo } } } In general, make sure to add id to all subselections of your queries.
Some time ago I came up with another solution, which is the same approach like @WuDo suggested. The idea is to flatten the tree on data level using IDs to reference them (each child with it’s parent) and marking the roots of the tree, then on client side build up the tree again recursively. This … Read more
In GraphQL, fields at each “level” of the request are executed and resolved in parallel. In your example, user and SomeOtherStuff are both fields of the same type (the root Query type) — so they will be resolved at the same time. That means each query essentially is not aware of the other or what … Read more
Apollo Client should work just fine on Node. You only have to install cross-fetch. Here is a complete TypeScript implementation of Apollo Client working on Node.js. import { ApolloClient, gql, HttpLink, InMemoryCache } from “@apollo/client”; import { InsertJob } from “./graphql-types”; import fetch from “cross-fetch”; const client = new ApolloClient({ link: new HttpLink({ uri: process.env.PRODUCTION_GRAPHQL_URL, … Read more
GraqhQL provides directives for this very purpose. Create a fragment to define common fields, use @include(if: Boolean) and @skip(if: Boolean) directives on that fragment to get dynamic fields. By dynamic fields we mean fields that are known at execution time. According to spec, it is best to avoid manual string interpolation to construct dynamic queries. … Read more
The biggest problem with your resolver is that in any number of scenarios, instead of returning a User object, you return a string. Your schema specifies that createAccount can return a User or null (if it was User!, it would be non-nullable and then null would not be a valid type either). When you return … Read more
The buildSchema function takes a schema in SDL (schema definition language) and returns a GraphQLSchema object. Given two identical schemas generated with each method, runtime performance would be the same. Startup time for a server using buildSchema would be slower since parsing the SDL adds an extra step that would not otherwise exist — whether … Read more