Firestore: fix watch against nested collections (issue #7515). #7613
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.
Fix for issue mentioned in the issue #7515, by replacing the parent info of query target from the url to the root of the database, to actual query parent, stored in its parent info.
Collection query holds an
_parent
variable pointing to the Document/CollectionReference, which holds info about database path in the_parent_info()
, which returns tuple containing:Thus, returning first value from
_parent_info()
, instead of url to root of database fixes the bug.