-
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
Canonization Options Not Passed via Diff #8831
Comments
benjamn
added a commit
that referenced
this issue
Sep 23, 2021
Both `returnPartialData` and `canonizeResults` were missing from this call. Instead of enumerating the properties, we can take advantage of the overlap between `WatchOptions` and `DiffOptions` to pass all properties through, without having to enumerate them explicitly, so this kind of mistake won't happen again. Fixes #8831.
benjamn
added a commit
that referenced
this issue
Sep 23, 2021
Both `returnPartialData` and `canonizeResults` were missing from this call. Instead of enumerating the properties, we can take advantage of the overlap between `WatchOptions` and `DiffOptions` to pass all properties through, without having to enumerate them explicitly, so this kind of mistake won't happen again. Fixes #8831.
benjamn
added a commit
that referenced
this issue
Sep 23, 2021
Both `returnPartialData` and `canonizeResults` were missing from this call. Instead of enumerating the properties, we can take advantage of the overlap between `WatchOptions` and `DiffOptions` to pass all properties through, without having to enumerate them explicitly, so this kind of mistake won't happen again. Fixes #8831.
benjamn
added a commit
that referenced
this issue
Sep 27, 2021
Both `returnPartialData` and `canonizeResults` were missing from this call. Instead of enumerating the properties, we can take advantage of the overlap between `WatchOptions` and `DiffOptions` to pass all properties through, without having to enumerate them explicitly, so this kind of mistake won't happen again. Fixes #8831.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Intended outcome:
Use the
canonizeResults
option to manually disable (or, after #8822, manually enable) canonization with theInMemoryCache
.Actual outcome:
While the customized value of
canonizeResults
is used in most situations, there are edge cases in which the default value ofcanonizeResults
is used instead.How to reproduce the issue:
Using the following configuration:
If you perform a query that involves
InMemoryCache
— and specifically, its privatebroadcastWatch
function — then custom values ofcanonizeResults
are not properly passed down.This is the offending call. The call to
diff
should pass alongc.canonizeResults
. This is closely related to work @benjamn is currently doing.Versions
The text was updated successfully, but these errors were encountered: