| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…dataconnect:generateApiTxtFile`
… to NOT be a breaking change
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Sorry, something went wrong.
Vertex AI Mock Responses Check ⚠️A newer major version of the mock responses for Vertex AI unit tests is available. update_responses.sh should be updated to clone the latest version of the responses: v5.2 |
Sorry, something went wrong.
|
The public api surface has changed for the subproject firebase-dataconnect: Please update the api.txt files for the subprojects being affected by this change by running ./gradlew ${subproject}:generateApiTxtFile. Also perform a major/minor bump accordingly. |
Sorry, something went wrong.
Coverage Report 1Affected Products
Test Logs |
Sorry, something went wrong.
Test Results 64 files - 972 64 suites - 972 1m 6s ⏱️ - 33m 19s Results for commit 7631f77. ± Comparison against base commit 2b072d9. This pull request removes 5332 and adds 1 tests. Note that renamed tests count towards both.com.google.android.datatransport.cct.CctBackendFactoryTest ‑ create_returnCCTBackend_WhenBackendNameIsCCT com.google.android.datatransport.cct.CctDestinationTest ‑ cctDestination_shouldOnlySupportProtoAndJson com.google.android.datatransport.cct.CctDestinationTest ‑ cctDestination_shouldSupportProtoAndJson com.google.android.datatransport.cct.CctTransportBackendTest ‑ decorate_whenOffline_shouldProperlyPopulateNetworkInfo com.google.android.datatransport.cct.CctTransportBackendTest ‑ decorate_whenOnline_shouldProperlyPopulateNetworkInfo com.google.android.datatransport.cct.CctTransportBackendTest ‑ schedule_shouldAddCookieOnPseudonymousIds com.google.android.datatransport.cct.CctTransportBackendTest ‑ schedule_shouldDropCookieOnMixedPseudonymousIds com.google.android.datatransport.cct.CctTransportBackendTest ‑ send_CompressedResponseIsUncompressed com.google.android.datatransport.cct.CctTransportBackendTest ‑ send_whenBackendRedirectsMoreThan5Times_shouldOnlyRedirect4Times com.google.android.datatransport.cct.CctTransportBackendTest ‑ send_whenBackendRedirects_shouldCorrectlyFollowTheRedirectViaPost … com.google.firebase.dataconnect.LoggerUnitTest ‑ noisiestOf() ♻️ This comment has been updated with latest results. |
Sorry, something went wrong.
|
The public api surface has changed for the subproject firebase-dataconnect: Please update the api.txt files for the subprojects being affected by this change by running ./gradlew ${subproject}:generateApiTxtFile. Also perform a major/minor bump accordingly. |
Sorry, something went wrong.
Size Report 1Affected Products
Test Logs |
Sorry, something went wrong.
…dataconnect:generateApiTxtFile`, changing StateFlow to Flow
|
I'm writing an API proposal for this PR, and, in doing so, will be changing a lot of the new API surface. Please hold off reviewing for now. |
Sorry, something went wrong.
|
The public api surface has changed for the subproject firebase-dataconnect: Please update the api.txt files for the subprojects being affected by this change by running ./gradlew ${subproject}:generateApiTxtFile. Also perform a major/minor bump accordingly. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Change the property FirebaseDataConnect.logLevel from LogLevel to MutableStateFlow<LogLevel>.
Being a MutableStateFlow enables applications to not only get and set its value, but also enables "collecting" the flow to be notified when its value changes. This can be useful, for example, to keep a UI element that reflects the log level (e.g. a "debug" checkbox) in sync with the actual log level in effect.
This PR also adds logcat messages to be emitted when the log level changes. This can be useful when examining logs after the fact to explain gaps in the logs (e.g. log level was unknowingly reduced to NONE, causing no logs to be emitted). The log messages look like this: