Compatible with the new Firebase?

[mbrevda]

It seems the js sdk has been updated with the latest v3 changes. Is this project still compatible?
Thanks!

[cpbotha]

Here's an (unofficial?) fork that seems to have firebase3 support: https://github.com/bobbyhubbard/backbonefire/tree/firebase3

Would be great to have official word from the GOOG mothership also!

[mbrevda]

Oh, cool. I hope someone can take a look!

[abeisgoat]

Hey folks - I'm working on bringing this into the Firebase 3.0 world - but since we need to migrate off of mockfirebase for our tests that means it's quite a bit of work.

It's coming soon, but no clear timeline.

[mbrevda]

Thanks @AbeHaskins. Anything new at your end re: this?

[mohansn]

Thanks, @AbeHaskins !

[mbrevda]

What are you using instead of mockfirebase?

[mstronge]

Hey @AbeHaskins - Any update on this? Thanks

[taseenb]

Is this project still maintained? Looks like it's abandoned. Thanks

[jpventura]

@taseenb, @AbeHaskins replied on twitter that the project is still maintained and that would make some updates next week.

Many development dependency libraries are deprecated, so I submitted the PR #158 updating them and fixing Travis CI test setup issues.

I don't know how long Firebase team will take to integrate the modifications, thus I have already integrated them into my fork

[AniX]

Is there any update regarding the progress? Thanks!

[jpventura]

@AbeHaskins, any updates on #158 ?

[mbrevda]

I don't believe this repo will be updated. Backbone is kind of outdated and if you can, you should probably consider using an up to date js lib. If you DO want to go with backbone, you should still look integrate backbone and firebase "manually" and not really on the magic this repo provided. From experience, that was a huge mistake.

[wuservices]

Perhaps the community could fork and maintain a version of this in a separate repo? I've seen a few forks already, but if it's hard to see what everybody's doing as a whole. Perhaps if starting from scratch Backbone may not be the go to, but with Marionette (still actively getting updates), it's still a pretty solid experience that can even get virtual DOM plugged in.

@mbrevda could you share a little more about why you'd go manual and not use this library if you were going Backbone? Would love to learn from your experience.

[mbrevda]

In a nutshell, there was too much "magic". Also, mapping a record to a collection/models as well as partial updates of a record works most of the time for some of the things... but just becomes more of a pain then it's worth. I found it way simpler to just set up listeners and then manually update collections/models (with the ability to normalize data as needed).