model.parse may no longer set the idAttribute

[tgriesser]

Getting rid of the temp models, should also fix some other issues, this assumes the idAttribute exists directly on the object used to construct the model, no longer allowing model.parse to dynamically set this property.

Note that collection.parse may still be used to prep this data on a fetch.

[caseywebdev]

👍

[mateusmaso]

hey @tgriesser, I found that you can't get rid of the temp models in a situation that your collection model is a method (only if you want to set a idAttribute inside the function prototype, which is a terrible idea I think). In that case your pull was leaving behind objects that were already in the collection but you didn't check the existence of it.

[braddunbar]

@mateusmaso I would look into overriding _prepareModel for that functionality instead.