Unfortunately, a type cannot be used in place of an input, and an input cannot be used in place of a type. This is by design. From the official specification: 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 … Read more
The props added by your firstQuery component will be available to the component below (inside) it, so you can do something like: export default compose( graphql(firstQuery, { name: ‘firstQuery’ }), graphql(secondQuery, { name: ‘secondQuery’, skip: ({ firstQuery }) => !firstQuery.data, options: ({firstQuery}) => ({ variables: { var1: firstQuery.data.someQuery.someValue } }) }) )(withRouter(TestPage)) Notice that we … Read more
There’s a better way to do it using the REST client Insomnia Docs are here, how to send graphql queries: https://support.insomnia.rest/article/61-graphql Below are the steps for postman Step 1. Run the GraphiQL in Chrome, open the Chrome Dev Console, click the Network tab, and make the query from graphiql, when you make the query, network … Read more
The issue is that given some query like “naruto”, your current code results in the following text: media(type:ANIME, search: naruto ) { This is not valid syntax since String literals should be surrounded by double quotes (“). Don’t use string interpolation to provide dynamic values to the query. These should always be expressed as variables … Read more
UPLOADS You don’t need to invent your own frontend code to add a file upload to a mutation — there are existing packages that do this already. For example, apollo-upload-client if you are using Apollo. To receive an uploaded file on the backend, the files are going to be available in the dictionary request.FILES. So … Read more
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
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
You’ll need to parse the info object that’s passed to the resolver as its fourth parameter. This is the type for the object: type GraphQLResolveInfo = { fieldName: string, fieldNodes: Array<Field>, returnType: GraphQLOutputType, parentType: GraphQLCompositeType, schema: GraphQLSchema, fragments: { [fragmentName: string]: FragmentDefinition }, rootValue: any, operation: OperationDefinition, variableValues: { [variableName: string]: any }, } You … Read more
Unfortunately what you’d like to do is not possible. GraphQL requires you to be explicit about specifying which fields you would like returned from your query.
These are tagged template literals. The part before the backpacks is a reference to a function that will be called to process the string. The function is passed the variables (the ${} parts) as arguments as well as the pieces of the string that surround the variables broken into an array. The return value of … Read more