Skip to content
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

Investigate decorating the lacinia schema #16

Open
oliyh opened this issue Nov 12, 2020 · 0 comments
Open

Investigate decorating the lacinia schema #16

oliyh opened this issue Nov 12, 2020 · 0 comments

Comments

@oliyh
Copy link
Owner

oliyh commented Nov 12, 2020

Imagine if a resolver B in the schema could also be given a bucket id, and all enqueues from that resolver would go into that bucket. If the parent resolver A could look ahead and see that B will be called as a child (one or more times) it should be possible to size the bucket for B based on the result of A * fields resolved by B.

I don't know if the context passed to a resolver contains enough information about the children to be able to get the bucket for B, or find how many child fields might use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant