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
Look at the documentation: const { graphqlHTTP } = require(‘express-graphql’); Note that it uses destructuring equivalent to: const graphqlHTTP = require(‘express-graphql’).graphqlHTTP; require(‘express-graphql’) returns an object with a property called graphqlHTTP that is the function you want to call. You’re trying to call the object itself as if it was a function.
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
Starting with the June2018 stable version of the GraphQL spec, an Object type can extend another Object type: Object type extensions are used to represent a type which has been extended from some original type. For example, this might be used to represent local data In your example, type Animal { species: String } extend … Read more
In GraphQL, an input cannot be used as a type and a type cannot be used as an input. Unfortunately, even if the fields appear identical to an existing type, you always have to define a separate input to use as an argument. Try something like this: const NotebookDetailsInput = new GraphQLInputObjectType({ name: ‘NotebookDetailsInput’, fields: … Read more
Apollo exposes two kinds of errors through its API: GraphQL errors, which are returned as part of the response as errors, alongside data, and network errors which occur when a request fails. A network error will occur when a server can’t be reached or if the response status is anything other than 200 — queries … Read more
The query name doesn’t have any meaning on the server whatsoever. It’s only used for clients to identify the responses (since you can send multiple queries/mutations in a single request). In fact, you can send just an anonymous query object if that’s the only thing in the GraphQL request (and doesn’t have any parameters): { … Read more
I have researched and also tried with Both GraphQL in Dot Net and Odata in DotNet Web API to create a working demo and What I found are Developer Usability Considering you have existing WebAPI(DotNet Framework) and want to migrate to GraphQL or OData compatible WebAPI then my answer is to choose OData because of … Read more
You can do it by passing a reference to Apollo Client using the withApollo higher-order-component, as documented here: https://www.apollographql.com/docs/react/api/react-apollo.html#withApollo Then, you can call client.query on the passed in object, like so: class MyComponent extends React.Component { runQuery() { this.props.client.query({ query: gql`…`, variables: { … }, }); } render() { … } } withApollo(MyComponent); Out of … Read more
From the docs: A GraphQL object type has a name and fields, but at some point those fields have to resolve to some concrete data. That’s where the scalar types come in: they represent the leaves of the query. GraphQL requires that you construct your queries in a way that only returns concrete data. Each … Read more