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
When useQuery is called by the component, it triggers the query subsequently. But when useLazyQuery is called, it does not trigger the query subsequently, and instead return a function that can be used to trigger the query manually. It is explained on this page: https://www.apollographql.com/docs/react/data/queries/#manual-execution-with-uselazyquery When React mounts and renders a component that calls the … Read more
Error and console.log surprises When trying to use console.log to view an error, you might be surprised to not see all the error data available. This is because console.log treats values which are instances of the built-in Error class in a special way, printing only the message, the type, and the stack. Apollo extends its … Read more
My preferred way is to use the compose functionality of the apollo client (docu). EDIT: If you have more than one query you should name them. So in your case, it could look like this: import React, {Component} from ‘react’ import queries from ‘./queries’ import { graphql, compose } from ‘react-apollo’; class Test extends Component … 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
The fault with my query was that I didn’t download the new schema. You can download the schema by using: apollo schema:download –endpoint=http://localhost:8080/graphql schema.json replace http://localhost:8080/graphql with your server endpoint You can see more at https://www.apollographql.com/docs/ios/downloading-schema/
Have a look at custom scalars: https://www.apollographql.com/docs/graphql-tools/scalars.html create a new scalar in your schema: scalar Date type MyType { created: Date } and create a new resolver: import { GraphQLScalarType } from ‘graphql’; import { Kind } from ‘graphql/language’; const resolverMap = { Date: new GraphQLScalarType({ name: ‘Date’, description: ‘Date custom scalar type’, parseValue(value) { … Read more
This is a known bug with an open issue and a merged PR to fix it. For now, you can downgrade to apollo-server-express@^2
As of the time of writing, there isn’t a built-in feature in GraphQL-JS or Apollo Server to handle this concern, but it’s something that should definitely have a simple solution as GraphQL becomes more popular. This concern can be addressed with several approaches at several levels of the stack, and should also always be combined … Read more
Non-null means exactly what it sounds like — not null. An empty array is not null — it’s still returning a value. Here is a summary table: declaration accepts: | null | [] | [null] | [{foo: ‘BAR’}] ———————————————————————— [Vote!]! | no | yes | no | yes [Vote]! | no | yes | yes … Read more