dvarjun
07/26/2017, 9:57 PMdvarjun
07/26/2017, 9:57 PMgidztech
07/26/2017, 10:11 PMdvarjun
07/26/2017, 10:16 PMdvarjun
07/26/2017, 10:16 PMdvarjun
07/26/2017, 10:16 PMzaksingh
07/26/2017, 10:33 PMvirtualirfan
07/26/2017, 11:54 PMtype MetaData {
algorithm: String!
}
type ABC implements Node {
createdAt: DateTime!
id: ID! @isUnique
test: MetaData!
updatedAt: DateTime!
}
I get an error:
test: The relation field `test` must specify a `@relation` directive: `@relation(name: "MyRelation")`
All I want to do is to specify a non-scalar type for a field without creating a new "table" that would create/necessitate a relation causing the equivalent of a join. Am I not thinking about this properly?
Thoughts?johhansantana
07/27/2017, 12:23 AMcomponentDidMount
?ryan
07/27/2017, 12:35 AM"Something unexpected happened in an Action: 'Query does not pass validation. Violations:\n\nCannot query field 'some_field' on type 'User'
, however, the user still gets created. I don’t have any permission (or query permission) configured on User type nor there’s “some_field” on it. Any ideas?mannigan
07/27/2017, 12:50 AMaarohmankad
07/27/2017, 12:54 AMfalconerd
07/27/2017, 4:44 AMgiven SomeType has fields a: String, b: Float
mutation createSomeType($data: SomeType!) {
createSomeType( <not sure what to put here> ) {
id
}
}
or do you have to list out each field separately twice?falconerd
07/27/2017, 4:51 AMmutation createCustomer(
$firstName: String!,
$lastName: String!,
$phoneNumber: String!,
$email: String,
) {
createCustomer(
firstName: $firstName,
lastName: $lastName,
phoneNumber: $phoneNumber,
email: $email,
) {
id
}
}
falconerd
07/27/2017, 4:51 AMfalconerd
07/27/2017, 4:51 AMmark_au
07/27/2017, 5:21 AMmark_au
07/27/2017, 5:42 AMfrankspin
07/27/2017, 7:31 AMtype User implements Node {
}
type Organization implements Node {
}
Now for the join table, what would be the best strategy? One type or two types?
type UserOrganizations implements Node {
}
type OrganizationUsers implements Node {
}
```frankspin
07/27/2017, 10:38 AMbogdan
07/27/2017, 11:05 AMquery allUsers($status: [USER_STATUS!]) {
allUsers(
filter:
{ status_in: $status }
) {
halborg
07/27/2017, 11:30 AMnephix
07/27/2017, 12:08 PMquery HasUserCompletedSetup($email: String!) {
User(email: $email) {
hasCompletedSetup
}
}
How can I set up the permission query so that users can only check their own data but no the data of other users?joeblack74
07/27/2017, 12:33 PMevents
on User)joeblack74
07/27/2017, 12:33 PMjoeblack74
07/27/2017, 12:33 PMjoeblack74
07/27/2017, 12:35 PMevent
field and not an events
list, I could simply do something like described in https://www.graph.cool/docs/reference/simple-api/creating-nodes-wooghee1za/?r#connecting-a-new-node-to-another-nodejoeblack74
07/27/2017, 12:35 PMjoeblack74
07/27/2017, 12:35 PMkarthikvarma
07/27/2017, 12:35 PM