You can use GraphQL Aliases to modify individual keys in the JSON response. If this is your original query query { POJO { id name } } you can introduce a GraphQL alias userName for the field name like so: query { POJO { id userName: name } } You can also use GraphQL aliases … Read more
Connections More powerful and flexible than simple lists. Support pagination (forward and back), with cursors. Fine-grained mutation support (eg. RANGE_ADD, RANGE_DELETE, NODE_DELETE, as described in the guide). Requires a first or last argument in order to limit the size of the result set. Has an edges field that provides a place to locate per-edge, edge-specific … Read more
Over-fetching is fetching too much data, meaning there is data in the response you don’t use. Under-fetching is not having enough data with a call to an endpoint, forcing you to call a second endpoint. In both cases, they are performance issues: you either use more bandwidth than ideal, or you are making more HTTP … Read more
Short Conventionally: Query — for querying data (SELECT operations) Mutation — for creating new and updating/deleting existing data (INSERT, UPDATE, DELETE) Detailed Technically any GraphQL query could be implemented to cause a data write. But there is a convention that any operations that cause writes should be sent explicitly via a mutation. Besides the difference … 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 `;
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
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
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
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
It looks like the grammar allows default values on input object types, so you can declare input ExampleInput { value: Int = 0 another: String isAvailable: Boolean = false } The spec is clear that default values exist and explains how they get used (first bullet under “Input Coercion”). (Whether any specific tooling supports this … Read more