dardub
09/01/2017, 12:59 AMdardub
09/01/2017, 1:07 AMjosxa
09/01/2017, 1:21 AMmlyons
09/01/2017, 1:36 AMaazlant
09/01/2017, 5:55 AMpicosam
09/01/2017, 7:17 AMSergey
09/01/2017, 7:29 AMcreateUser
mutation return error with this user is already addedshahfahad
09/01/2017, 8:10 AMkuldar
09/01/2017, 11:37 AMreact-apollo
to a component state on component load. What would be the best way for doing that? Accessing props.data
doesn't seem to work in componentDidMount()
senorcodecat
09/01/2017, 1:10 PMpeterp
09/01/2017, 1:17 PMpeterp
09/01/2017, 1:17 PMpeterp
09/01/2017, 1:17 PMyolen
09/01/2017, 2:08 PMpicosam
09/01/2017, 4:39 PMgraphcool-cli
does not yet support this out of the box.kennet
09/01/2017, 4:53 PMkennet
09/01/2017, 4:53 PMrvespula
09/01/2017, 5:04 PMrvespula
09/01/2017, 5:04 PMnilan
09/01/2017, 5:12 PMagentbond007
09/01/2017, 5:53 PMpeterp
09/01/2017, 6:12 PMpeterp
09/01/2017, 6:12 PMpeterp
09/01/2017, 6:13 PMjvbianchi
09/01/2017, 6:24 PMstephenhandley
09/01/2017, 6:25 PMTRANSFORM_ARGUMENT
function which would get invoked after initial schema validation.
https://www.graph.cool/docs/reference/functions/request-pipeline/transform-input-arguments-caich7oeph/
For another project backed by a thin model layer in front of MongoDB using Apollo Server, I've been doing some validation using custom scalars as described here:
http://dev.apollodata.com/tools/graphql-tools/scalars.html
I've also come across this proposal for input type validation extension to GraphQL spec
https://github.com/graphql/graphql-js/issues/361
Wondering what people's thoughts are on the different alternatives..mwickett
09/01/2017, 6:38 PMnilan
09/01/2017, 9:13 PMjstephen
09/01/2017, 9:14 PMnilan
09/01/2017, 9:20 PM