Which Backbone versions work with RESTe?
icecandy opened this issue · comments
Simon Buckingham commented
Just a query, but what versions of Backbone is RESTe designed to work with?
I only ask because use of Backbone in Alloy has a compatibility issue when using Backbone version 1.1.2 where one has to modify the model definition:
extendCollection: function(Collection)
{
_.extend(Collection.prototype,
{
// extended functions and properties go here
// For Backbone v1.1.2, uncomment the following to override the
// fetch method to account for a breaking change in Backbone.
fetch: function(_options)
{
_options = _options ? _.clone(_options) :
{};
_options.reset = true;
return Backbone.Collection.prototype.fetch.call(this, _options);
},
.........
And specify the version in config.json:
"backbone": "1.1.2"
Jason Kneen commented
Uses the bultin. Never had to extend a model or collection definition in practice. What’s the reason / need?
…-- jason
On Monday, Aug 20, 2018 at 13:38, Simon Buckingham ***@***.*** ***@***.***)> wrote:
Just a query, but what versions of Backbone is RESTe designed to work with?
I only ask because use of Backbone in Alloy has a compatibility issue when using Backbone version 1.1.2 where one has to modify the model definition:
extendCollection: function(Collection)
{
_.extend(Collection.prototype,
{
// extended functions and properties go here
// For Backbone v1.1.2, uncomment the following to override the // fetch method to account for a breaking change in Backbone. fetch: function(_options) { _options = _options ? _.clone(_options) : {}; _options.reset = true; return Backbone.Collection.prototype.fetch.call(this, _options); },
.........
And specify the version in config.json:
"backbone": "1.1.2"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (#71), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAeo8vVqC-3a1n4nE5ED2V8qT_svl1RNks5uSq2vgaJpZM4WD6th).