-
Notifications
You must be signed in to change notification settings - Fork 897
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
get()
server data must be indexed
#4796
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 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 Report |
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
jmwski
changed the title
May 11, 2021
get()
server data must be indexed + transaction fixget()
server data must be indexed
schmidt-sebastian
approved these changes
May 11, 2021
Binary Size ReportAffected SDKs
Test Logs |
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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::updateFullNode
on 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
repoOnDataUpdate
I also noticed that we should probably be callingrepoRerunTransactions
when server data comes in for the first time (though I'm not certain here).