Repository navigation
fix: flutterfire configure command when existing firebase_options.dart has a wrong format - #424
Merged
russellwheatley merged 4 commits intoMar 31, 2026
Conversation
…art` has a wrong format
nilsreichardt
had a problem deploying
to
CI Environment
February 26, 2026 17:04 — with
GitHub Actions
Failure
nilsreichardt
had a problem deploying
to
CI Environment
February 26, 2026 17:04 — with
GitHub Actions
Failure
nilsreichardt
had a problem deploying
to
CI Environment
February 26, 2026 17:04 — with
GitHub Actions
Failure
1 task done
nilsreichardt
had a problem deploying
to
CI Environment
March 3, 2026 15:59 — with
GitHub Actions
Failure
nilsreichardt
had a problem deploying
to
CI Environment
March 3, 2026 15:59 — with
GitHub Actions
Failure
nilsreichardt
had a problem deploying
to
CI Environment
March 3, 2026 15:59 — with
GitHub Actions
Failure
russellwheatley
temporarily deployed
to
CI Environment
March 30, 2026 18:00 — with
GitHub Actions
Inactive
russellwheatley
temporarily deployed
to
CI Environment
March 30, 2026 18:00 — with
GitHub Actions
Inactive
russellwheatley
temporarily deployed
to
CI Environment
March 30, 2026 18:00 — with
GitHub Actions
Inactive
Member
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request improves the robustness of the Firebase configuration file generation by allowing the CLI to regenerate the file if it detects placeholder content (e.g., UnimplementedError). It introduces a helper method _buildConfigurationFile to centralize the generation logic and adds a regression test to verify that placeholder files are correctly replaced. The review feedback suggests applying the formatList utility within the new helper method to ensure consistent file formatting, which has been incorporated into the suggested improvement.
russellwheatley
temporarily deployed
to
CI Environment
March 31, 2026 09:32 — with
GitHub Actions
Inactive
russellwheatley
temporarily deployed
to
CI Environment
March 31, 2026 09:32 — with
GitHub Actions
Inactive
russellwheatley
temporarily deployed
to
CI Environment
March 31, 2026 09:32 — with
GitHub Actions
Inactive
Member
|
@nilsreichardt - thank you for PR, sorry for the delay. I'll merge once it goes green 🙏 |
russellwheatley
approved these changes
Mar 31, 2026
1 of 7 tasks
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
If the repository already had a
firebase_options.dartfile, theflutterfire configurecommend expected a specific format. If this file had a different format, theflutterfire configure .command failed.As described in #422 the example of flutter/ai repository has this
firebase_options.dart:Source: https://github.com/flutter/ai/blob/fd3d6d7936f503e9e53d91564cb280263083c1bf/example/lib/firebase_options.dart
Before this PR, the
flutterfire configurecommand couldn't handle thisfirebase_options.dartfile.Closes #422
Type of Change
feat-- New feature (non-breaking change which adds functionality)fix-- Bug fix (non-breaking change which fixes an issue)!-- Breaking change (fix or feature that would cause existing functionality to change)refactor-- Code refactorci-- Build configuration changedocs-- Documentationchore-- Chore