Connection with edge data

[michaelbeaumont]

We're trying to tweak graphql-compose-connection to add data to the edges.
Concretely, we have an m-to-n relationship in mongo linking to collections X and Y using a collection XY which has data itself:

XY = new mongoose.Schema({
  xId: ObjectId,
  yId: ObjectId,
  kind: String,
})

Ideally, I'd like to have the following schema:

xs {
  <x fields>
  ys {
    edges {
      kind  // <- comes from `XY`
      node {
        <y fields>
      }
    }
  }
}

How could graphql-compose-connection support this?

Some things aren't clear, like how to do filtering, how to deal with indexes.

Our current idea for filtering would allow for something like:

ys(filter: { node: {<y fields>}, edge: { kind: "kind1" } }) {

where I can do filtering both on the edge and the node.

What do you think? We have a WIP

[nodkz]

For such complex case, I recommend you write field resolver from scratch. It will be faster and more configurable.

Also, you may try to use addRelation method:

• Keep the "filter" arg with an addRelation() that prepares that filter arg graphql-compose#94
• [Feature] Add ability to pass fieldConfig to addRelation method. graphql-compose#43

But I found that addRelations complex in some situations and it's may lead to some complex debuggable situations.

So don't get in trap with code generation with such case. Just write such resolver manually and you save your time.

[nodkz]

For such complex case, I recommend you write field resolver from scratch. It will be faster and more configurable.

Also, you may try to use addRelation method:

• Keep the "filter" arg with an addRelation() that prepares that filter arg graphql-compose#94
• [Feature] Add ability to pass fieldConfig to addRelation method. graphql-compose#43

But I found that addRelations complex in some situations and it's may lead to some complex debuggable situations.

So don't get in trap with code generation with such case. Just write such resolver manually and you save your time.

[michaelbeaumont]

The point of using connection would be to get all of the pagination, cursor etc "for free".
My plan at the moment is to write the resolver manually, but some tweaks to connection are needed, for creating the edge type and tweaking the output to match that type.

[nodkz]

Open PR and let discuss proposed changes.

PS. we should try to keep runtime changes as small as possible for this package. we should try to avoid performance degradation.

[PeteMac88]

Open PR and let discuss proposed changes.

PS. we should try to keep runtime changes as small as possible for this package. we should try to avoid performance degradation.

Hey, any news when you will have a look at the proposed changes in the PR?

[nodkz]

@michaelbeaumont sorry for the delay. I completely lose your PR. Sorry! 🙏
@PeteMac88 thanks for pinging me 👍

[nodkz]

🎉 This issue has been resolved in version 6.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀