CODEWITHSUNDEEP
javascriptmodel-view-controllerbackbone.jsbackbone-model
AlexZ
AlexZ

Reputation: 12073

In BackboneJS, clarification on setting the attributes of models

Two common scenarios when I am using backbone backbone:

Attribute is listed as default value, then set

modelExample_A: Backbone.Model.extend({
  defaults: {
    whatever: 'foo'
    something: 'blah'
  }
});

viewExample_A: Backbone.View.extend({
  //our view definition
});

var Example_A = new viewExample_A({
  model: new modelExample_A()
})
Example_A.set({
  'whatever': 'bar',
  'something': 'weeeeeee',
});

Attribute is not listed as a default value, then set

modelExample_A: Backbone.Model.extend({
});

viewExample_A: Backbone.View.extend({
  //our view definition
});

var Example_A = new viewExample_A({
  model: new modelExample_A()
})
Example_A.set({
  'whatever': 'bar',
  'something': 'weeeeeee',
});

Attribute is not listed as a default value, set on creation

modelExample_A: Backbone.Model.extend({
});

viewExample_A: Backbone.View.extend({
  //our view definition
});

var Example_A = new viewExample_A({
  model: new modelExample_A({
    'whatever': 'bar',
    'something': 'weeeeeee',
  })
})

But what about situations where I want to set a property of the model? I know this is generally discouraged, but sometimes in my code I like to make a not of a what model is the parent of the current model. This is something that almost certainly won't ever change, so there is no reason to put in the attribute for event listening/onChange purposes. Further, this is something without a default value (it can only get a value in context), so is it okay to just set it as a property of the model? Or will this cause problems down the line?

Setting a property instead of an attribute

modelExample_A: Backbone.Model.extend({
  defaults: {
    whatever: 'foo'
    something: 'blah'
  }
});

viewExample_A: Backbone.View.extend({
  //our view definition
});

var Example_A = new viewExample_A({
  model: new modelExample_A({
    'whatever': 'bar',
    'something': 'weeeeeee',
  })
})
Example_A.parentModel = parentModelExample;

Upvotes: 0

Views: 96

Answers (1)

Peter Lyons
Peter Lyons

Reputation: 146054

Used in moderation and with consideration, setting non-attribute properties on model instances is fine. Just be careful not to have this be data that can easily get into an inconsistent state, and if you are doing this a lot, that's a code smell. In that case, you may want to consider modeling some state as actual models with attributes, but just not persisting them (never call .save).

Upvotes: 3

Related Questions