Skip to content

chore(fdc): Use service classes to fetch auth and appcheck instances#18263

Merged
aashishpatil-g merged 4 commits intomainfrom
ap/authAppCheckService
May 8, 2026
Merged

chore(fdc): Use service classes to fetch auth and appcheck instances#18263
aashishpatil-g merged 4 commits intomainfrom
ap/authAppCheckService

Conversation

@aashishpatil-g
Copy link
Copy Markdown
Contributor

Use service resolvers to get auth and app check parameters.

@aashishpatil-g aashishpatil-g requested a review from cynthiajoan May 7, 2026 18:27
@gemini-code-assist
Copy link
Copy Markdown
Contributor

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 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 .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 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.

@aashishpatil-g
Copy link
Copy Markdown
Contributor Author

/gemini review

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request deprecates the explicit passing of FirebaseAuth and FirebaseAppCheck instances in the FirebaseDataConnect constructor and instanceFor method, transitioning to automatic internal handling via the FirebaseApp service registry. It also includes updated mocks and new tests to verify dynamic service discovery. Feedback was provided to update the class fields directly during transport initialization to ensure state consistency instead of relying on local variables.

Comment on lines +218 to +219
auth ??= app.getService<FirebaseAuth>();
appCheck ??= app.getService<FirebaseAppCheck>();
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bit of changing the behavior. The previous is if auth and appcheck is not passed in, instantiate one and put that. The changed code will be, if auth and appCheck is not passed in, assign it with an already registered auth/appcheck instance. If they are not instantiated, it will still keep null.

But also the previous behavior doesn't config auth and appcheck after instantiated. What is the expected thing here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverted to the previous behavior.

@aashishpatil-g aashishpatil-g merged commit 5a2afd2 into main May 8, 2026
32 of 35 checks passed
@aashishpatil-g aashishpatil-g deleted the ap/authAppCheckService branch May 8, 2026 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants