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
The idea is that Backbone-relational should not replace Collection.model if it's something custom wrote by user. This means that user knows that it should return and instance of relatedModel but he wants to do there some clever logic. Backbone-relational should allow him to have a custom Collection.model.
The text was updated successfully, but these errors were encountered:
Our application uses clever
Backbone.Collection.model()
because we store in collection different types of models. We have "dynamic"relatedModel
.I made a (mini copy) demo of our application to demonstrate how it works and where is the problem.
Here it is
Here it uses my fixed version of Backbone-relational
The idea is that Backbone-relational should not replace
Collection.model
if it's something custom wrote by user. This means that user knows that it should return and instance ofrelatedModel
but he wants to do there some clever logic. Backbone-relational should allow him to have a customCollection.model
.The text was updated successfully, but these errors were encountered: