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
I think some of these could be merged into one: FieldResolutionContext, FieldResult, SelectionResult. They all form a tree which corresponds to the final result. Merging them would open some interesting doors:
Deferred/streaming execution (if nodes retain their runtime objects and know how to continue executing themselves, a bit like ExecFrame from Defer directive #168)
Also, it would be a performance improvement due to fewer allocations (#861)
I don't have a priority for this; I want to get a few features finished out first. But I thought I'd open the issue so people know that the idea is out there!
The text was updated successfully, but these errors were encountered:
There are a lot of non-user-facing objects created to resolve a GraphQL query:
I think some of these could be merged into one: FieldResolutionContext, FieldResult, SelectionResult. They all form a tree which corresponds to the final result. Merging them would open some interesting doors:
Also, it would be a performance improvement due to fewer allocations (#861)
I don't have a priority for this; I want to get a few features finished out first. But I thought I'd open the issue so people know that the idea is out there!
The text was updated successfully, but these errors were encountered: