Skip to content

[AppCheck] Recaptcha: use site key from FirebaseOptions#8221

Open
rlazo wants to merge 2 commits into
mainfrom
rl.recaptcha.sitekey
Open

[AppCheck] Recaptcha: use site key from FirebaseOptions#8221
rlazo wants to merge 2 commits into
mainfrom
rl.recaptcha.sitekey

Conversation

@rlazo
Copy link
Copy Markdown
Contributor

@rlazo rlazo commented May 27, 2026

Removed the requirement to provide the site key manually during instantiation of RecaptchaEnterpriseAppCheckProviderFactory. The factory now retrieves the site key directly from FirebaseOptions via the FirebaseApp instance provided during the create method.

Removed the requirement to provide the site key manually during
instantiation of RecaptchaEnterpriseAppCheckProviderFactory. The
factory now retrieves the site key directly from FirebaseOptions via
the FirebaseApp instance provided during the create method.
@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.

@rlazo
Copy link
Copy Markdown
Contributor Author

rlazo commented May 27, 2026

/gemini review

@rlazo rlazo requested a review from emilypgoogle May 27, 2026 21:39
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 refactors RecaptchaEnterpriseAppCheckProviderFactory to remove the siteKey parameter from its constructor and getInstance() method, instead retrieving it dynamically from FirebaseApp options during provider creation. Corresponding updates were made to the API definition, gradle dependencies, and unit tests. A review comment points out that caching the provider instance variable in the factory is now redundant and introduces a potential state-sharing bug in multi-app environments, suggesting that the factory should be made completely stateless.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 27, 2026

📝 PRs merging into main branch

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

@google-oss-bot
Copy link
Copy Markdown
Collaborator

1 Warning
⚠️ Did you forget to add a changelog entry? (Add the 'no-changelog' label to the PR to silence this warning.)

Generated by 🚫 Danger

@rlazo rlazo requested a review from VinayGuthal May 27, 2026 22:54
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.

2 participants