notrab
03/29/2017, 5:30 PMnotrab
03/29/2017, 5:31 PMartyom
03/29/2017, 5:45 PMbrucelane
03/29/2017, 6:08 PMmel
03/29/2017, 6:44 PMts
03/29/2017, 7:30 PMts
03/29/2017, 7:30 PMts
03/29/2017, 7:31 PMmannigan
03/30/2017, 1:36 AMhvillain
03/30/2017, 1:42 AMjleonard
03/30/2017, 4:45 AMtype TwoWayLeft {
id: ID!
one: TwoWayRight! // ! (required) and [] (list) thrown in for extra complication
two: [TwoWayRight] // although even plain (modifier-free) fields would seem problematic.
}
type TwoWayRight {
id: ID!
three: TwoWayLeft
four: TwoWayLeft
}
[or any number of similar problematic (from a data modeling perspective) cases].
How would graphcool know which fields on each side correspond to fields on the other side in order to setup the foreign keys/relationships in the underlying physical database schema (Postgres/SQL or NoSQL or what have you)?qsys
03/30/2017, 1:28 PMauth0
generated JWT. If a new user is created on auth0
, and permissions/groups/roles are added in auth0
, can we use these authorization-fields in graphQL? How?hagai.co
03/30/2017, 2:53 PMtim2
03/30/2017, 2:56 PMtim2
03/30/2017, 2:57 PMmannigan
03/30/2017, 4:26 PMqsys
03/30/2017, 8:03 PMAgent
and that has a relation with a User
(some kind of mixin/interface would make more sense, but that's not supported yet, and I suppose build-in types such as User
and File
will not be interfaces π ). However, I would like to make the user-field in Agent
required (each Agent is a user), but this doesn't seem to be possible right now, or is it?sanyaade
03/30/2017, 10:17 PMhvillain
03/31/2017, 2:26 AMjaydenseric
03/31/2017, 5:32 AMdataknut
03/31/2017, 7:44 AMartyom
03/31/2017, 9:50 AMferamon
03/31/2017, 11:09 AMferamon
03/31/2017, 11:10 AMschickling
03/31/2017, 11:19 AMferamon
03/31/2017, 11:21 AMferamon
03/31/2017, 11:21 AMferamon
03/31/2017, 11:22 AMferamon
03/31/2017, 11:22 AMartyom
03/31/2017, 2:20 PM