mcierpicki
04/02/2018, 7:54 PMpasa
04/02/2018, 11:02 PMpasa
04/02/2018, 11:04 PMjoelseq
04/02/2018, 11:50 PMpasa
04/02/2018, 11:52 PMjoelseq
04/02/2018, 11:53 PMjoelseq
04/02/2018, 11:53 PMjoelseq
04/02/2018, 11:53 PMpasa
04/02/2018, 11:54 PMdigitaltopo
04/03/2018, 1:14 AMhamatek
04/03/2018, 2:01 AMtaikn
04/03/2018, 6:57 AM1.5.2
release a few days ago, is it already available on npm? đź‘€alexc
04/03/2018, 9:07 AMerror.graphQLErrors[0].functionError.response.errors[0].message
. Is there any reason why this message isn’t returned by default instead of the more generic function execution error
?Vendicto
04/03/2018, 9:55 AMdrizzie
04/03/2018, 12:10 PMdrizzie
04/03/2018, 12:10 PMMoritz
04/03/2018, 12:48 PMtype Image {
id: ID! @unique
createdAt: DateTime!
updatedAt: DateTime!
...
}
type Story {
id: ID! @unique
createdAt: DateTime!
updatedAt: DateTime!
image: Image!
}
type Post {
id: ID! @unique
createdAt: DateTime!
updatedAt: DateTime!
image: Image!
}
Now, I will only access the Image
type as a nested parameter through the other (story, post) endpoints. However, I still would like to define a custom resolver on the server side that allways is called when another resolver accesses the image to return a default image in certain cases. Where/how would I define this? Thanks!
PS: When doing this only for one resolver it works fine like this: import { Context } from "../utils";
export const Story = {
image: async (parent, args, ctx: Context, info) => {
return ...
}
};
However, I would like to apply this custom resolver to all images, not just the one being called from Story.Moritz
04/03/2018, 2:19 PMlefevre
04/03/2018, 3:40 PMtype ParentObject @model {
id: ID! @isUnique
child: ChildObject
@relation(name: "ChildObjectOnParentObject")
property1: String
}
type ChildObject @model {
id: ID! @isUnique
parent: ParentObject! @relation(name: "ChildObjectOnParentObject")
property2: String
}
Using Graphcool framework and the relay spec, is it possible in one mutation to update property1 of the parent and it's the related childs property2 or does it have to be two seperate update mutations? 🙂Soniiqaah
04/03/2018, 4:15 PMSoniiqaah
04/03/2018, 4:17 PMmax
04/03/2018, 5:25 PMmichrob
04/03/2018, 5:53 PMmichrob
04/03/2018, 5:54 PMDan Caddigan
04/03/2018, 6:14 PMajmakhl
04/03/2018, 6:34 PM{
"data": {
"push": null
},
"errors": [
{
"message": "Whoops. Looks like an internal server error. Please contact us from the Console (<https://console.graph.cool>) or via email (support@graph.cool) and include your Request ID: eu-west-1:system:...",
"requestId": "eu-west-1:system:...",
"path": [
"push"
],
"locations": [
{
"line": 2,
"column": 9
}
]
}
],
"status": 200
}
wesbos
04/03/2018, 7:14 PMwesbos
04/03/2018, 7:14 PMkristiansorens
04/03/2018, 7:17 PMlawjolla
04/03/2018, 9:40 PMupdateMany
and deleteMany
do not trigger subscription events?