The Node root field, in combination with globally unique IDs, comes into play when Relay needs to refetch an object. Refetching occurs when you call this.props.relay.forceFetch() or when you add fields to the query for an object whose global ID is known because it has already been partially fetched. In cases like these, Relay will … Read more
You are missing a closing bracket } at the end of your query. const GET_VEHICLE_CHECKS = gql` query getVehicleChecks($uuid: String!) { tripDetails(uuid: $uuid){ departmentAssigned{ vehicleChecks{ conditions{ id name standard valueType spinnerItems } } } } } <- THIS `;
In the GraphQL spec, objects and input objects are distinct things. Quoting the spec for input objects: Fields can define arguments that the client passes up with the query, to configure their behavior. These inputs can be Strings or Enums, but they sometimes need to be more complex than this. The Object type… is inappropriate … Read more
You can definitely query with an array of values! Here’s what the query itself would look like: { events(containsId: [1,2,3]) { … } } And the type would look something like: const eventsType = new GraphQLObjectType({ name: ‘events’, type: // your type definition for events, args: { containsId: new GraphQLList(GraphQLID) }, … }); If you … Read more
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
I had a similar error. I worked it out by adding id to query. for example, my current query was query { service:me { productServices { id title } } } my new query was query { service:me { id // <——- productServices { id title } } }
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
There are two uses of … related to fragments. Incorporating a fragment by reference query Foo { user(id: 4) { …userFields } } fragment userFields on User { name } Has the effect of composing the fields from the fragment into the embedding query: query Foo { user(id: 4) { name } } Note that … Read more
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