-
Notifications
You must be signed in to change notification settings - Fork 989
get() server data must be indexed
#4796
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
Conversation
🦋 Changeset detectedLatest commit: 0ef4c5b The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Size Analysis ReportAffected ProductsNo changes between base commit (997040a) and head commit (750e2688). Test Logs |
schmidt-sebastian
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also add a changelog
get() server data must be indexed + transaction fixget() server data must be indexed
Binary Size ReportAffected SDKs
Test Logs
|
If we're getting data from the server, it should be indexed with the query param index.
For the value event registration path, I think the query index is applied using
IndexFilter::updateFullNodeon the filter attached to the view that the listener sets up front.Experimentally, even when the query results are already cached (even if they don't have the same path index), as in:
get()will add the new path index to theCacheNode's index map. It's only in the case where data comes in from the server for the first time that we'd see this issue.Side note: Looking at
repoOnDataUpdateI also noticed that we should probably be callingrepoRerunTransactionswhen server data comes in for the first time (though I'm not certain here).