-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection with edge data #50
Comments
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
But I found that So don't get in trap with code generation with such case. Just write such resolver manually and you save your time. |
1 similar comment
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
But I found that So don't get in trap with code generation with such case. Just write such resolver manually and you save your time. |
The point of using connection would be to get all of the pagination, cursor etc "for free". |
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? |
* Add ability to add fields to edges * Add connectionResolver with edgeFields to tests
@michaelbeaumont sorry for the delay. I completely lose your PR. Sorry! 🙏 |
🎉 This issue has been resolved in version 6.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
andY
using a collectionXY
which has data itself:Ideally, I'd like to have the following schema:
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:
where I can do filtering both on the edge and the node.
What do you think? We have a WIP
The text was updated successfully, but these errors were encountered: