I ran into this problem as well. It appears that what you’re returning from your resolver doesn’t match the return type in your schema. Specifically for the error message Expected Iterable, but did not find one for field library.user., your schema expects an array(Iterable) but you aren’t returning an array in your resolver I had … Read more
Update Using graphql-cli is now the recommended workflow to get and update your schema. The following commands will get you started: # install via NPM npm install -g graphql-cli # Setup your .graphqlconfig file (configure endpoints + schema path) graphql init # Download the schema from the server graphql get-schema You can even listen for … Read more
Disadvantages: You need to learn how to set up GraphQL. The ecosystem is still rapidly evolving so you have to keep up. You need to send the queries from the client, you can just send strings but if you want more comfort and caching you’ll use a client library -> extra code in your client … Read more
That means that the field is non-nullable. See more info in Graphql – Schemas and Types
From the spec: The GraphQL Object type (ObjectTypeDefinition)… is inappropriate for re‐use [as an input], because Object types can contain fields that define arguments or contain references to interfaces and unions, neither of which is appropriate for use as an input argument. For this reason, input objects have a separate type in the system. That’s … Read more
Let’s begin with a short introduction in simple words GraphQl Relay specifications mechanism for refetching an object description of how to page through connections structure around mutations to make them predictable Connections: a connection is a collection of objects with metadata such as edges, pageInfo… pageInfo will contain hasNextPage, hasPreviousPage, startCursor, endCursor hasNextPage will tell … Read more
Change .mockReturnValue with .mockImplementation: yourMockInstance.mockImplementation(() => { throw new Error(); }); in case you want to assert test(‘the fetch fails with an error’, () => { return expect(fetchData()).rejects.toMatch(‘error’); }); If it’s a promise you can also to .rejects www.jestjs.io/docs/en/asynchronous#resolves–rejects
I have viewed the Angular Air Episode 26: FalcorJS and Angular 2 where Jafar Husain answers how GraphQL compares to FalcorJS. This is the summary (paraphrasing): FalcorJS and GraphQL are tackling the same problem (querying data, managing data). The important distinction is that GraphQL is a query language and FalcorJS is not. When you are … Read more
If you are using Linux, your project is hitting your system’s file watchers limit To fix this, on your terminal, try: echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Definitely approach #1. Having your clients talk to multiple GraphQL services (as in approach #2) entirely defeats the purpose of using GraphQL in the first place, which is to provide a schema over your entire application data to allow fetching it in a single roundtrip. Having a shared nothing architecture might seem reasonable from the … Read more