Martin Peck
11/30/2017, 4:36 PMButch
11/30/2017, 5:36 PMEmi
11/30/2017, 5:41 PMmichaelchiche
11/30/2017, 5:50 PMgraphcool deploy --dry-run
, it always tells me my functions are wrong but graphcool deploy
works fine, and the functions work correctly?huv1k
11/30/2017, 5:50 PMorr
11/30/2017, 5:54 PM/me
endpoint as seen in many APIs. As per Graphcool's online examples, issuing a query from a resolver to the CRUD Api for the logged in user would look something like this:
const query = `
query me($id: ID!) {
viewer {
User(id: $id) {
< fields from the client go here >
}
}
}
`;
const variables = {
id: event.context.auth.nodeId,
};
const api = fromEvent(event).api('relay/v1');
const response = await api.request(
query,
variables,
);
My question is: Is there a more idiomatic way to do this in Graphcool? And would it make sense for the client to pass up a variable (potentially named fragment
) that will be used inside the query to fetch the fields the client is interested in?doug_w
11/30/2017, 5:55 PMdoug_w
11/30/2017, 6:05 PMv4.8.6
philip
11/30/2017, 8:47 PMoprearocks
11/30/2017, 9:49 PMoprearocks
11/30/2017, 9:49 PMGraham Ballantyne
12/01/2017, 12:53 AMoperationBefore
) fire in response to a change in a relationship? For example, I have Department
and Employee
types, and a relationship between the two to define managers. I want a hook to fire in response to the addToDepartmentManagers
mutation. I've tried hooking into both Department.update
and Employee.update
operations but neither get triggered.Graham Ballantyne
12/01/2017, 12:59 AMAddToDepartmentManagersPayload
, but that causes deploy
to throw an error.Lam Kieu
12/01/2017, 1:38 AMTrung Tròn Trịa
12/01/2017, 1:55 AMrizaSatyabudhi
12/01/2017, 3:21 AMlazypatch
12/01/2017, 4:42 AMTyler
12/01/2017, 6:22 AMbnilsen
12/01/2017, 8:16 AMsegebee
12/01/2017, 8:45 AMsegebee
12/01/2017, 8:45 AMsegebee
12/01/2017, 8:57 AMsegebee
12/01/2017, 8:57 AMBilal K
12/01/2017, 8:59 AMChinCluBi
12/01/2017, 9:29 AMsoftware.amazon.awssdk.services.lambda.model.InvalidParameterValueException: Error occurred while GetObject. S3 Error Code: NoSuchKey. S3 Error Message: The specified key does not exist. (Service: null; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: 04091ee3-d67a-11e7-96e1-cb885ab22331)
cloudpilot
12/01/2017, 12:19 PMcloudpilot
12/01/2017, 12:21 PMlefevre
12/01/2017, 12:47 PMdale
12/01/2017, 1:07 PMgraphql-playground-middleware-lambda: 1.3.0
and i'm seeing this error.user
12/01/2017, 1:09 PMhttps://prisma.slack.com/files/U8961PS78/F88E21HGV/screen_shot_2017-12-01_at_13.05.55.pngâ–¾