react-fullstack-graphql issues

Running signup mutation results in error

3

> Error: Field “createUser” of type “User!” must have a selection of subfields. Did you mean “createUser { ... }“? ```graphql mutation { signup(email:“[email protected]”,name:“test”,password:“test1234”) { token } } ```

marktani

bug

Adding a client folder to the boilerplate

2

This is half question, half suggestion, but wouldn't it make sense for this boilerplate code to have its own client folder with its own package.json file?

elie222

Check Node version in `.install/index.js`

1

I've noticed several individuals asking for help when using the boilerplates. The source of the recurring problem is dangling commas, which aren't recognized until Node 8. Node 8 is now...

DevanB

help wanted

Refactor ApolloClient instantiation to new apollo-boost syntax

1

The advanced boilerplate has a lot of the older non-apollo-boost way of setting up the ApolloClient. For the purposes of helping others who might be new to Apollo and GraphQL,...

DevanB

help wanted

made the User field in AuthPayload optional

@marktani @manjula91 This should fix this issue https://github.com/graphql-boilerplates/react-fullstack-graphql/issues/359 * It was happening because User is an Object and was marked as required field in schema of AuthPayload. Now it's made...

vivek12345

Readme for minimal setup updated

* Readme for minimal setup updated with detailed instruction on installing graphql-cli * Commands for starting GraphQL server and Client added. * Node compatibility version information added. @marktani @manjula91 Please...

vivek12345

Use nodemon for start script

1

I've noticed that in the front-end related graphql-boilerplates, we are asking users to start the front-end application and open another tab to start the server. I propose we change the...

DevanB