Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

feat: Add forRoot & forFeature

See original GitHub issue

I.e. ngrx has forRoot & forFeature https://stackoverflow.com/questions/46348412/what-is-the-difference-between-storemodule-forroot-and-storemodule-forfeature

For FirebaseUI-Angular by having .forRoot that initialises in the AppModule, we could also have an instance of .forFeature that is being used for lazy loaded feature modules. So this would be possible to also use <firebase-ui></firebase-ui> in other lazy loaded modules.

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:15 (14 by maintainers)

Top GitHub Comments

2reactions

RaphaelJennicommented, Jun 17, 2018

So I finally had some time to check this issue. The plugin works this way anyway. You initialize the module in the main module with forRoot, in every other (lazy loaded) module you import it without the forRoot.

You can read more about that in here: https://medium.com/@chrishouse/when-to-use-angulars-forroot-method-400094a0ebb7

The forFeature is only ngrx to import some further sub stores. This isn’t needed here.

1reaction

RaphaelJennicommented, Jun 7, 2018

I will look into it as soon as I find the time.