express-graphql

问题 I am trying to use Apollo Server's Upload scalar to send files to S3 directly. My schema: const { gql } = require('apollo-server-express') module.exports = gql` extend type Mutation { createPicture( name: String! picture: Upload! ): Picture! } type Picture { name: String! picture: String! } ` Resolver: const { combineResolvers } = require('graphql-resolvers') const isAuthenticated = require('./auth') const { uploadPhoto } = require('../services/picture') module.exports = { Mutation: {

问题 I am trying to use Apollo Server's Upload scalar to send files to S3 directly. My schema: const { gql } = require('apollo-server-express') module.exports = gql` extend type Mutation { createPicture( name: String! picture: Upload! ): Picture! } type Picture { name: String! picture: String! } ` Resolver: const { combineResolvers } = require('graphql-resolvers') const isAuthenticated = require('./auth') const { uploadPhoto } = require('../services/picture') module.exports = { Mutation: {

来源： https://stackoverflow.com/questions/53078554/how-to-implement-istypeof-method

来源： https://stackoverflow.com/questions/53078554/how-to-implement-istypeof-method

问题 I am trying to make a mutation to my Shopify store from python. I am new to graphQL, I have been able to make the mutation using graphiQL but I am not certain how to do it directly from my code. This is my make query file, it has worked successfully for a simple query `import requests def make_query(self, query, url, headers): """ Return query response """ request = requests.post(url, json={'query': query}, headers=headers) if request.status_code == 200: return request.json() else: raise

问题 Here is my simple graphql experess app const express = require('express'); const graphqlHTTP = require('express-graphql'); const app = express(); app.use( '/graphql', graphqlHTTP({ graphiql: true, }) ); app.listen(4000, () => { console.log("listening for request!"); }); I'm getting the following errors when I run it: graphqlHTTP({ ^ TypeError: graphqlHTTP is not a function at Object.<anonymous> (D:\PersonalProjects\GraphQL\server\app.js:7:5) at Module._compile (internal/modules/cjs/loader.js

问题 I have this code: const ProductType = new GraphQLObjectType({ name: 'Product', fields: { id: { type: GraphQLID }, name: { type: GraphQLString }, category: { type: CategoryType, resolve: async (parent) => { return await Category.findOne({_id: parent.category}); } } } }); const CategoryType = new GraphQLObjectType({ name: 'Category', fields: { id: { type: GraphQLID }, name: { type: GraphQLString }, products: { type: ProductType, resolve: async (parent, args) => { return await Product.find(

问题 In an express-graphql app, I have a userLogin resolver like so: const userLogin = async ({ id, password }), context, info) => { if (!id) { throw new Error('No id provided.') } if (!password) { throw new Error('No password provided.') } // actual resolver logic here // … } If the user doesn't provide an id AND a password , it will throw only one error. { "errors": [ { "message": "No id provided.", "locations": [ { "line": 2, "column": 3 } ], "path": [ "userLogin" ] } ], "data": { "userLogin":

问题 In an express-graphql app, I have a userLogin resolver like so: const userLogin = async ({ id, password }), context, info) => { if (!id) { throw new Error('No id provided.') } if (!password) { throw new Error('No password provided.') } // actual resolver logic here // … } If the user doesn't provide an id AND a password , it will throw only one error. { "errors": [ { "message": "No id provided.", "locations": [ { "line": 2, "column": 3 } ], "path": [ "userLogin" ] } ], "data": { "userLogin":

问题 Can someone help me on this, My setup was as follows prior to Apollo 2.0, I had a server.js in which i used express and graphql-server-express I had a http only cookie session, when a user logs in I set the jwt token as a cookie and it is set in browser as http only. On subsequent request I validate the cookie that the browser passes back. It was all working fine and I could access the token from req.session.token in any other resolver and validate the jwt token saved in the cookie session.