This repository was archived by the owner on Aug 25, 2018. It is now read-only.
Removed Bacbone.sync override #82
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to the 0.4 release a new Backbone.Mode could be created with a
firebase
attribute.This behavior is being removed in the 0.4 release. The reasoning behind this decision was due to the confusion of the separate components:
Backbone.Firebase.Model
andBackbone.Model.extend({ firebase: ''});
Going forward all of the functionality BackFire provides will be in the
Backbone.Firebase
namespace. There will still be an option that allows for data to not automatically be synced. In those cases you will be able to callsync()
,save()
,fetch()
, and etc...This will leave the core of Backbone untouched, while hopefully reducing confusion.