joao.santos
11/14/2017, 12:15 PMtype PatientProfile @model {
createdAt: DateTime!
id: ID! @isUnique
updatedAt: DateTime!
name: String!
number: Int! @isUnique
lastName: String
lastViewed: String
patientDocumentation: PatientDocumentation @relation(name: "DocumentationOnPatient")
}
type PatientDocumentation @model {
hours12: String
id: ID! @isUnique
natural: String
patientProfile: PatientProfile @relation(name: "DocumentationOnPatient")
profile: String
video: String
withdrawn: String
xray: String
}
huv1k
11/14/2017, 1:23 PMMODULES
and want to use it in *.graphql
and *.js
files.alexanbj
11/14/2017, 1:51 PMSallyP
11/14/2017, 3:17 PMSallyP
11/14/2017, 3:17 PMChris S
11/14/2017, 3:26 PMsteveb
11/14/2017, 3:29 PMstarsinmypockets
11/14/2017, 4:01 PMgraphcool init --schema <https://graphqlbin.com/hn-starter.graphql> --name Hackernews
give me the error Unknown flag --schema
koddsson
11/14/2017, 4:01 PMgraphql-cli
. It seems to have been updated on master
but not published to npm. Could someone cut a patch release to npm? 🙏bwoodlt
11/14/2017, 4:02 PM[object object]
when I ran my graphql
subscriptions
?divyendu
11/14/2017, 4:26 PMdonedgardo
11/14/2017, 5:02 PMemattias
11/14/2017, 5:02 PMmerchant {
foo{
bar {
baz{
baa
}
}
}
}
and bar
does not exists, should the response be an object containing baz
and baa
keys (and baa
is null
) or should bar
be equal to null
? What is recommended graphql behavior?emattias
11/14/2017, 5:08 PM{
"data": {
"foo": {
"bar": null
}
}
}
or
{
"data": {
"foo": {
"bar": {
"baz": {
"baa": null
}
}
}
}
}
jeff
11/14/2017, 5:11 PMjeff
11/14/2017, 5:11 PMarvin
11/14/2017, 5:20 PMarvin
11/14/2017, 5:22 PMgraphcool init
graphcool deploy
it doesn't show up.
It's only there if I start a new project from the website graph.coolsteveb
11/14/2017, 6:42 PMschickling
11/14/2017, 7:40 PMgerardsans
11/14/2017, 7:41 PMgerardsans
11/14/2017, 7:42 PMbobbyt
11/14/2017, 7:45 PMconst newMessageSubscription = gql`
subscription {
Message(filter: { mutation_in: [CREATED, UPDATED] }) {
node {
id
text
createdAt
sentBy {
id
name
}
receivedBy {
id
name
}
}
}
}
`;
This works (data is returned) when a new message arrives or an existing message field is updated (i.e., text
field). However, if a subfield such as receivedBy
is updated on the server (indicating another user has read the message), the subscription does not return anything. Thanks in advance!taizo
11/15/2017, 1:24 AMiamclaytonray
11/15/2017, 1:52 AMdata
object in my component’s constructor()
. Does anyone know of an elegant way to do this? I haven’t tried wrapping it in a HOC yet so I’ll do that, which should work, but maybe someone has some insight that would help outmatty
11/15/2017, 6:36 AMmatty
11/15/2017, 6:37 AMmatty
11/15/2017, 6:37 AMmatty
11/15/2017, 6:37 AMmatty
11/15/2017, 7:08 AM