Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions src/content/ai/ai-toolkit/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -233,11 +233,6 @@ details into the `example/lib/firebase_options.dart` file. You can do this with
the `flutterfire CLI` tool as described in the [Add Firebase to your Flutter
app][add-fb] docs **from within the `example` directory**.

Copy link
Contributor

Choose a reason for hiding this comment

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

medium

While removing the incorrect warning is a good step, it would be even more helpful for users to replace it with a note explaining why it's safe to commit firebase_options.dart. This would clarify Firebase's security model and prevent user confusion, echoing the useful context you provided in the pull request description.

Suggested change
::::
note It is **safe to check the `firebase_options.dart` file** into your version control system. While it contains project identifiers, it does not include private keys or other sensitive data. Access to your Firebase backend is controlled by [Firebase Security Rules](https://firebase.google.com/support/guides/security-checklist).
::::

Copy link
Contributor

Choose a reason for hiding this comment

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

@nilsreichardt, this is a draft, so I leave this up to you, but it does seem like a good suggestion.

:::
note **Be careful not to check the `firebase_options.dart` file into your git
repo.**
:::

## Feedback

Along the way, as you use this package, please [log issues and feature
Expand Down
Loading