-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
The "newly" added read/merge functions from typePolicies are not async like the old local resolvers #9895
Comments
I suspect that risks a significant performance penalty, and is probably exactly why they removed the old APIs |
I fail to see where is the perf penalty in this case. Except that the cache update action will be delayed until the promise is resolved. The old resolver was slower because you could call queries from async resolvers which led to cache duplication |
This is a duplicate of apollographql/apollo-feature-requests#383 which contains more discussion/info. Please follow the other issue for updates on this topic, closing. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
We are trying to migrate from apollo client 2.x to 3.x. One of the challenges we are facing is the fact that the old local async resolves cannot be migrated to the newly added read/merge functions.
Potential solution: make read/merge async.
The text was updated successfully, but these errors were encountered: