Firestore: minor update to docs for experimentalAutoDetectLongPolling #7306
Conversation
This file contains hidden or 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
… and version when its default value was changed to `true`
|
Size Report 1Affected ProductsNo changes between base commit (e12e7f5) and merge commit (8114a3f).Test Logs |
Size Analysis Report 1Affected ProductsNo changes between base commit (e12e7f5) and merge commit (f27f471).Test Logs |
ehsannas
approved these changes
May 18, 2023
ehsannas
approved these changes
May 18, 2023
dconeybe
requested review from
egilmorez,
markarndt,
kevinthecheung and
a team
as code owners
markarndt
approved these changes
May 18, 2023
dconeybe
deleted the
dconeybe/AutoDetectLongPollingEnabledByDefaultUpdateDocsWithVersion
branch
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.
This PR updates the documentation of
FirestoreSettings.experimentalAutoDetectLongPollingto state the exact month and version at which its default value changed totrue(wasfalsesince its introduction 4 years ago in 2019). This is a follow-up to #7236, which changed its default value and was released in v9.22.0 on May 12, 2023.