You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When specifying a relation with 2 different node types on both ends (e.g. Movie and Actor), this relation can be used inside Movie or Actor and gets correct direction (depending on from/to values in relation).
If both ends of a relation have the same type, there currently seems to be no way to indicate which "side" of the relation a field should relate to. See an example below:
type User {
name:String
referredBy: Referral @relation(direction: OUT)
referred:[Referral] @relation(direction: IN)
}
type Referral @relation (name:"REFERRED_BY", from:"user", to: "referredBy" ) {
user:User
referredBy:User
referralDate:String
}
At the moment, generated query will use outgoing relationship for both referredBy and referred
The text was updated successfully, but these errors were encountered:
When specifying a relation with 2 different node types on both ends (e.g. Movie and Actor), this relation can be used inside Movie or Actor and gets correct direction (depending on from/to values in relation).
If both ends of a relation have the same type, there currently seems to be no way to indicate which "side" of the relation a field should relate to. See an example below:
At the moment, generated query will use outgoing relationship for both referredBy and referred
The text was updated successfully, but these errors were encountered: