One to Many properties relationship

[amaster507 (Anthony Master)]

@outsidertrading

Could one put two properties inside the @hasInverse, for example?

loans [Loan] @hasInverse(field: lender, borrower)

This is possible, (at least it was. It is undocumented, and I am no longer using. Not sure if there are tests under the hood to check for this functionality, so I would not use it in production myself)
See:

@amaster507

On a side note, You can create some wonky relationships like this:

posts: [Post] @hasInverse(field: user, field: likes)

BUT!! That may cause more problems down the road, FYI.

I have found that it can lead to a big problem with trying to do some kind of indexing on the edges. I just stopped trying to do these “three-way” relationships and just stick to two-way relationships.

type Loan {
  id: ID!
  value: String!
  currency: String!
  lender: Member!
  borrower: Member!
}

type Member {
  id: ID!
  cordaNodeName: String
  borrowed: [Loan] @hasInverse(field: "borrower")
  lended: [Loan] @hasInverse(field: "lender")
}

@outsidertrading

I see I could actually do outLoans and inLoans with two separate [Loan] lists

When possible try to name the edges more appropiately, you will thank yourself later when trying to remember which was an inLoan and outLoan actually go. lended and borrowed makes more sense as the edge names in this context.