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
{{ message }}
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.
Currently, if the field resolvers don't use a sophisticated distinctUntilChanged on their value or if they don't work with immutable data structures we will emit too many change events, because if something deep in the tree changes we will have combineLatest fire too often.
We are in a position to mitigate this problem: We have all the type information from the schema, so we can just traverse the schema and whenever we find a primitive we can wrap it with distinctUntilChanged.
I would love to hide this behavior behind a flag, as the comparison might have more toll on the performance then emitting too many events
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, if the field resolvers don't use a sophisticated
distinctUntilChanged
on their value or if they don't work with immutable data structures we will emit too many change events, because if something deep in the tree changes we will havecombineLatest
fire too often.We are in a position to mitigate this problem: We have all the type information from the schema, so we can just traverse the schema and whenever we find a primitive we can wrap it with
distinctUntilChanged
.I would love to hide this behavior behind a flag, as the comparison might have more toll on the performance then emitting too many events
The text was updated successfully, but these errors were encountered: