Angularfire: support firebase 7 with @angular/fire

[johanchouquet]

Hi,

This is not a bug but a feature request.

In order to benefit the latest goodies of Firebase for the web (remote config, analytics and extensions), it'd be so great that @angular/fire would support Firebase 7.

Do you plan on working on that anytime soon ?

Thanks a lot.

[jamesdaniels]

WIP here #2187. Let me know what you think of the API.

[johanchouquet]

Hi @jamesdaniels , i'll do that. Awesome!

[Dan203]

So when is this going to go live? I would like to use some of these features in a new app I'm working on but it doesn't look like there is a release with this change yet.

[doczoidberg]

API looks good for me

[jamesdaniels]

@Dan203 I'll have a release in the next week. Taking a couple days of R&R after getting back from the Firebase Summit roadshow.

[doczoidberg]

@jamesdaniels any news?

[tgangso]

when can we expect this?

[almothafar]

So, any news about the release, it was expected to have it from about 2 weeks ago.

[jamesdaniels]

I've addressed the peer warning and I've fixed the zone.js issues that were plaguing #2187. Turns out they were affecting the 5.2.1 release too, if you upgraded Firebase and ignored the peer warning. I've fixed these in 5.2.3 (1c3e423, let's just skip over 5.2.2... 😇)

With that out of the way, I'll continue to work on the new features.

[tgangso]

@jamesdaniels

Great, would you mind elaborating on the zone.js issues, what problem did it cause for end users?

[johanchouquet]

Great news! Thanks a lot @jamesdaniels !

About the imminent release of Angular 9, do you think Ivy will have a huge impact of how the library is built ? Hopefully not

[jamesdaniels]

@tgangso if you injected either FirebaseApp with Firebase v7 or brought in AngularFirePerformanceModule then your app would never stabilize, disrupting service workers, making SSR impossible, and leading to general (but subtle) mayhem 😛

@johanchouquet I think ng 9 and Ivy will influence us moving forward but I don't foresee any breaks for the time being. I've started including basic ng 9 tests and I have a PR in which I've moved over to ngc building the library but haven't finished due to red tests. I'll be prioritizing that after 5.3. For risk of breaking I might just include that in version 6; which I foresee as 99% API compatible. I'll just be dropping compatibility with older Angular, Typescript, and Firebase versions.

[tgangso]

@jamesdaniels thanks for fixing it, I have been using both and have had some weird subtle issues, maybe this will fix it.

[johanchouquet]

@johanchouquet I think ng 9 and Ivy will influence us moving forward but I don't foresee any breaks for the time being. I've started including basic ng 9 tests and I have a PR in which I've moved over to ngc building the library but haven't finished due to red tests. I'll be prioritizing that after 5.3. For risk of breaking I might just include that in version 6; which I foresee as 99% API compatible. I'll just be dropping compatibility with older Angular, Typescript, and Firebase versions.

Releaved to know that our code base would likely not be too much disturbed. Thanks a lot for the clarifications @jamesdaniels !

[matheo]

Thanks a lot @jamesdaniels
I've been missing the 5.3 release :)