Dojo declare - the scope of default properties (instance or static)

Question

I've spent a lot of time debugging strage error in my component. That component have disabled/enabled buttons, but I haven't seen the effect. After a while, I've noticed, the buttons are changed in the last component instance I've created. The declaration looks so:

  constructor: function(options) {
    for(var i in options){
      this[i] = options[i];
    }
  },
  domNode: null,
  grid: null,
  data: [],
  buttons: {},

In the debug, I've seen, that when I create second instance of my object:

new CustomComponent({domNode: dojo.byId('secondid')})

the buttons are already set - their instance is shared by all instances!

In end effect, I've created a static variable in my component. This is not what I wanted! What is wrong in that declaration? How should I made 'buttons' instance separate for each component instance?

Answer 1

I suppose that CustomComponent is a widget? Then you're doing some stuff wrong. The thing you do in your constructor (I suppose that's to populate your widget properties?) is not even necessary since that's already there by default when you use dijit/_WidgetBase.

Same with your property domNode, it's also there already by default if you use dijit/_WidgetBase.

My guess is that by overriding the constructor to act like this, you're actually doing some steps that the WidgetBase should do and thus messing up the private scope of the properties.

An example widget:

var CustomComponent = declare("my/CustomComponent", [WidgetBase], {
    grid: null,
    data: [],
    buttons: {}
});

This code does exactly the same as your widget and is a lot shorter.

An example JSFiddle that has instance scoped properties (as you can see in the console log).