chore: update migration guide, Angular and React example apps on how to use FirebaseUI v7 without fetchSignInMethodsForEmail()

[russellwheatley]

For: #1313

This shows the new example flow. I signed in with google before attempting to sign-in incorrectly with email provider:

recording.of.react.example.mov

[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 provides crucial updates for developers migrating to FirebaseUI v7, specifically addressing the deprecation of fetchSignInMethodsForEmail(). It introduces a new, secure pattern for handling sign-in provider mismatches, ensuring users are guided to the correct authentication method without relying on the deprecated API. The changes include comprehensive documentation in the migration guide and practical, runnable examples in both Angular and React applications, demonstrating how to implement provider tracking and hint mechanisms.

Highlights

• Migration Guide Update: The MIGRATION.md file has been updated with a new section addressing the deprecation of fetchSignInMethodsForEmail() in FirebaseUI v7, providing guidance on how to handle sign-in provider mismatches securely.
• New Angular Example Components: Two new Angular components, SignInWithProviderTrackingComponent and ProviderHintComponent, have been added to demonstrate the recommended approach for tracking sign-in providers and guiding users to the correct authentication method.
• New React Example Components: Corresponding React components, SignInWithProviderTrackingPage and ProviderHintPage, have been introduced to showcase the same provider tracking pattern within a React application.
• Dependency Management Update: The .gitignore file was updated to include .pnpm-store, ensuring proper exclusion of pnpm-related artifacts.

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

Changelog

• .gitignore
  • Added .pnpm-store to the ignore list.
• MIGRATION.md
  • Added a new section detailing the deprecation of fetchSignInMethodsForEmail() and outlining recommended approaches for handling sign-in provider mismatches.
  • Provided code examples for tracking providers using localStorage and discussed more secure production alternatives like HttpOnly cookies or hashed identifiers.
• examples/angular/src/app/routes.ts
  • Added new routes for the SignInWithProviderTrackingComponent and ProviderHintComponent to the Angular example application.
• examples/angular/src/app/screens/provider-hint.ts
  • Added a new Angular component (ProviderHintComponent) to display appropriate OAuth sign-in buttons based on stored provider hints.
• examples/angular/src/app/screens/sign-in-with-provider-tracking.ts
  • Added a new Angular component (SignInWithProviderTrackingComponent) demonstrating how to track sign-in providers and handle credential errors.
• examples/react/src/firebase/firebase.ts
  • Commented out the connectAuthEmulator call in development mode.
• examples/react/src/routes.ts
  • Added new routes for the SignInWithProviderTrackingPage and ProviderHintPage to the React example application.
• examples/react/src/screens/provider-hint.tsx
  • Added a new React component (ProviderHintPage) to display appropriate OAuth sign-in buttons based on stored provider hints.
• examples/react/src/screens/sign-in-with-provider-tracking.tsx
  • Added a new React component (SignInWithProviderTrackingPage) demonstrating how to track sign-in providers and handle credential errors.

Activity

• Closed issue Trying to log in with Email+Password when already logged in with OAuth previously only shows "Incorrect password" #1313.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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 provides a comprehensive solution for the deprecation of fetchSignInMethodsForEmail, including detailed documentation in MIGRATION.md and functional examples in both Angular and React applications. The changes are well-structured and the code is of high quality. I've suggested a couple of minor improvements to the documentation to ensure it is fully consistent with the example implementations.