You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 25, 2018. It is now read-only.
This Collection initializes models with an attribute. Create() works as expected, including the attribute in the object. Add() uses only the passed-in data.
A non-Firebase-extended collection returns the expected content using add():
I imagine this is because Backfire create() uses
model = Backbone.Collection.prototype._prepareModel.apply(this, [model, options]);
while add() does not.
It's not clear if the difference is a feature, or an oversight.
The text was updated successfully, but these errors were encountered:
Try to contact backbone and investigate SO questions; see if there is any definitive answer to the roles of add vs. create. Then specify our version of these behaviors in the README and make sure we are consistent (which will probably be done as part of #10)
This Collection initializes models with an attribute. Create() works as expected, including the attribute in the object. Add() uses only the passed-in data.
A non-Firebase-extended collection returns the expected content using add():
I imagine this is because Backfire create() uses
while add() does not.
It's not clear if the difference is a feature, or an oversight.
The text was updated successfully, but these errors were encountered: