Repository navigation
Add firebase-crashlytics-telemetry-compose - #8673
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
|
Did you forget to add a changelog entry? (Add the 'no-changelog' label to the PR or 'NO_RELEASE_CHANGE' to the description to silence this warning.) |
6ed056d to
3dbd499
Compare
9804859 to
40b716e
Compare
2ddea2f to
30961db
Compare
f7fa2bb to
6f711f9
Compare
Adds ScreenTracker(name), which records a composable as a screen when it
enters the composition, and NavHostController.trackNavigation(), which
records each Navigation destination. Also renames
FirebaseCrashlyticsTelemetry.logScreenAppear to recordScreenAppear for
consistency with recordClick, and removes the coordinate overload of
recordClick.
Destinations are named by their route pattern, such as
`profile/{userId}`, so argument values are never recorded. Compose lives
in its own library so apps that do not use Compose do not take on those
dependencies.
Tested by unit tests
6f711f9 to
9ea5685
Compare
28615a7
into
firebase-crashlytics-telemetry
3 participants
Adds ScreenTracker(name), which reports a composable as a screen while its lifecycle is resumed, and NavHostController.trackNavigation(), which reports each Navigation destination.
Tested by unit tests