Providers and Injections should be by name or at least by Map<string,type> and not by a simple Array<type>
- Vorherrschende Sprache
- TypeScript
- Sterne
- 7.8k
- Forks
- 2.2k
- Ø Merge
- 22 Std. 28 Min.
- Gemergte PRs (30 T.)
- 6
Beschreibung
### Version info
**Angular:** 14.2
**Firebase:** 9.9.3
**AngularFire:** 7.4.1
**Other (e.g. Ionic/Cordova, Node, browser, operating system):** Irrelevant
### Expected behavior
Provide / Injection by name or Map where the string is the name to find easy and clean your angular firebase components or have a function to findByName(name: string).
I'm not talking only about Auth, I'm talking regarding all your types but I use Auth for the examples
``` typescript
@NgModule({
imports: [
provideFirebaseApp(() => initializeApp(config)), // default app
provideFirebaseApp(() => initializeApp(config2, 'app2')),
provideFirebaseApp(() => initializeApp(config3, 'app3')),
provideAuth(() => getAuth()), // from default app
provideAuth(() => getAuth(getApp('app2'))),
provideAuth(() => getAuth(getApp('app3'))),
],
})
```
One of the next options should be there to be use it easy:
**Option 1** - Could be work with your actual Array but I think that search this search byName in this array is dirty and I recommend to not reinvent the wheel and use a Map
``` typescript
constructor(
private authApp: Auth,
private authApp2: AuthInstances.getByName('app2'),
private authApp3: AuthInstances.getByName('app3'),
) { }
```
**Option 2** - Could be work with your actual Array but again I recommend to not reinvent the wheel and use a Map
``` typescript
constructor(private authInstances: AuthInstances) { }
doWithAuth(name: string) {
const auth = this.authInstances.getByName(name)
// the things that you want to do with your auth
}
```
**Other options** - Any idea that let you select your angular fire element more easy and clean that now.
### Actual behavior
Provide / Injection is a simple Array and does not have any method to select by name.
``` typescript
@NgModule({
imports: [
provideFirebaseApp(() => initializeApp(config)), // default app
provideFirebaseApp(() => initializeApp(config2, 'app2')),
provideFirebaseApp(() => initializeApp(config3, 'app3')),
provideAuth(() => getAuth()), // from default app
provideAuth(() => getAuth(getApp('app2'))),
provideAuth(() => getAuth(getApp('app3'))),
],
})
```
``` typescript
private authMap: Map;
constructor(private authInstances: AuthInstances) {
this.authInstances.forEach(auth => {
this.authMap.set(auth.name,auth);
});
}
```
### Feedback
I think that your Provide / Injection should work with maps or with something that can be select the future injection by name.
Another important thing, is that you must declare a default app, if not the AuthInstaces fail because default app is not initializate and then to find this default app is so ugly `name: "[DEFAULT]"`
To finish, you cannot import only one auth if your auth is not default, because you have a way to import default and to import an array with default and another auths. Is there a way to inject `auth: Auth` by name and avoid import all the array?
Issue post from discussion: _Originally posted by @todosybuenrollo in https://github.com/angular/angularfire/discussions/1026#discussioncomment-3613308_
Beitragsleitfaden
Rechercherichtung
Beginne damit, die im Issue beschriebenen Einstiegspunkte provideFirebaseApp, provideAuth und AuthInstances nachzuverfolgen, einschließlich der Auflösung von standardmäßigen und benannten Firebase-Apps. Überprüfe das aktuelle Injection-Verhalten und die zugehörigen Tests, sofern vorhanden, bevor du dich zwischen benannter Injection und einer map-basierten API entscheidest. Erledigt ist die Aufgabe, wenn Verbraucher nicht standardmäßige Auth-Instanzen anhand ihres Namens auswählen können, ohne manuell ein Array durchsuchen zu müssen, und dabei das Verhalten der Standard-App erhalten bleibt.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- angular, firebase, typescript
- Bereich
- backend-api-design
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 28/100