docs: Refactor analytics import and usage in documentation

[NaNtrack]

Description

Updated import and usage of the analytics module

Related issues

None

Release Summary

Updated import and usage of analytics functions

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
  • Other (macOS, web)
• My change includes tests;
  • e2e tests added or updated in packages/\*\*/e2e
  • jest tests added or updated in packages/\*\*/__tests__
• I have updated TypeScript types that are affected by my change.
• This is a breaking change;
  • Yes
  • No

Test Plan

No test plans needed

[vercel]

@NaNtrack is attempting to deploy a commit to the Invertase Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the way the @react-native-firebase/analytics module is imported and utilized within the documentation examples. The changes update the code snippets to leverage named imports for specific analytics functions and pass the analytics instance explicitly, ensuring the documentation reflects the current best practices for interacting with the analytics module.

Highlights

• Analytics Import Refactoring: Updated the import statements for the analytics module from a default import to named imports for specific functions like getAnalytics, logEvent, and logSelectContent.
• Analytics Usage Modernization: Refactored the usage of analytics functions, moving from method chaining on a default imported instance (e.g., analytics().logEvent()) to passing an explicitly obtained analytics instance as the first argument to named imported functions (e.g., logEvent(analyticsInstance, ...)).
• Documentation Examples Updated: All relevant code examples within the analytics usage documentation were updated to align with the new import and usage patterns.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize 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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. 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.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the analytics usage examples in the documentation to use the new modular API. The changes are mostly correct and improve the documentation by showcasing the modern API. I've found one point of inconsistency in the usage of getAppInstanceId compared to other functions and left a suggestion to make it consistent with the rest of the examples.