-
Notifications
You must be signed in to change notification settings - Fork 893
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
Update CHANGELOG.md to mention limbo resolution throttling #2864
Conversation
This change to the change log was forgotten in the PR that added throttling: #2790
/retest |
packages/firestore/CHANGELOG.md
Outdated
@@ -1,4 +1,9 @@ | |||
# Unreleased | |||
- [changed] Limbo resolution now attempts to resolve a maximum of 100 documents |
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.
Changelogs are hard. They end up in our release notes: https://firebase.google.com/support/release-notes/js so they should be comprehensible by our end users.
This note has some problems:
- "Limbo resolution" is not an end-user concept we've documented.
- There's too much detail ("resource exhausted", 15,000)
- It links to the PR and the issue we're fixing, when one is sufficient
So the way to write this is to think about what we're doing on users' behalf when performing limbo resolution. At a high level we're "resolving cache inconsistencies" or "resolving inconsistencies in the local cache".
How about:
Firestore now limits the number of concurrent document lookups it will perform when resolving inconsistencies in the local cache (#2683).
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.
Done. I like how you said the same thing with 50% fewer words :)
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.
LGTM
This change to the change log was forgotten in the PR that added throttling: #2790