Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FirebaseOptions interface has all of its properties set to optional #7603

Open
marcusx2 opened this issue Sep 4, 2023 · 2 comments
Open

Comments

@marcusx2
Copy link

marcusx2 commented Sep 4, 2023

Operating System

macOS

Browser Version

Safari 16.5.2

Firebase SDK Version

10.1.0

Firebase SDK Product:

Auth

Describe your project's tooling

index.html with source tag.

Describe the problem

I am talking about this interface

export interface FirebaseOptions {
  apiKey?: string;
  authDomain?: string;
  databaseURL?: string;
  projectId?: string;
  storageBucket?: string;
  messagingSenderId?: string;
  appId?: string;
  measurementId?: string;
}

All of the properties are optional, however from the docs only measurementId should be.

Steps and code to reproduce issue

See https://firebase.google.com/docs/reference/js/app.firebaseoptions.

@marcusx2 marcusx2 added new A new issue that hasn't be categoirzed as question, bug or feature request question labels Sep 4, 2023
@jbalidiong jbalidiong added api: core needs-attention and removed api: auth new A new issue that hasn't be categoirzed as question, bug or feature request labels Sep 4, 2023
@jbalidiong
Copy link
Contributor

Hi Marcus, thanks for reaching out to us. I was able to verify the inconsistency in our documentation. I’ll notify our team about this so that they can take a look.

@hsubox76
Copy link
Contributor

Please don't spam questions about how to use APIs across multiple unrelated issues. The appropriate channels for that are Firebase Support for support, and for help building your app, community sites like Stack Overflow and other Firebase user communities. We also have a Discussions page in this repo that's better fitted for open ended discussions with other users. There's nothing wrong with user questions, and we will try to answer any that are asked in the appropriate forum, when we have time, but we need to keep the issues section limited to bugs and feature requests, or it will become difficult to triage and address bugs in a timely manner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants