we actually do have a token API that the console uses. We would have to implement it here as well but perhaps we could point users to that method instead of the console

How can configure this for testing against our internal testing endpoints or emulator?

The expectation is that you call getStorage(app, 'myendpoint') or getStorage(undefined, 'myEndpoint')

I'm curious how other SDKs handle env overrides. Could you confirm this is commonly how this is implemented?

Firestore just uses the google cloud package and does something like this:

 const settings: Settings = {
  host: "localhost:8080",
  ssl: false
};

// Initialize Firestore
const firestore = new Firestore(settings);

For RTDB, we ask them to override the databaseUrl:

admin.initializeApp({
    credential: admin.credential.cert(serviceAccount),
    databaseURL: "https://movie-picker-729bb-default-rtdb.firebaseio.com",
  });

So I don't think there's a best practices way to get this done. My recommendation is to do something like:

getStorage({ host: 'myhosturl' });

So that we can allow for more options to be customized down the road. WDYT?

EDIT: Introducing a new ENV var seems cleaner than piping through a bunch of classes. WDYT?

Ack, I don't have a strong sense of what design is right here, env var sounds fine.

Eventually these patterns should be consolidated imo, but that can happen async.

should this be private?

seems like there's a bug here, getFirebaseMetadata above assumes this.endpoint has the /v0 url part.

update

Did you want me to add more information about this?

typo: Firebase

Since we already have one for the emulator host, does it make sense to use another env var for the endpoint override?

remove

is this comment still accurate?

https://tsdoc.org/pages/tags/throws/

Please update with a description of the result or remove as this is redundant with the method signature

update?

update?

small nit: jsdoc clauses unnecessary unless they add context that cant be inferred from the method signature

go/java-practices/javadoc#param

same comment

is this comment still up to date?

update?

update tests