JetView extends vs protoUI => code more clear => webix powa

Webix JS
#1

Got lot’s of headeck mixing protoUI and JetView.

With protoUI, the config object in $init is modified because of mixins.

Does the code below is the good one in a webix-jet context ?

On my side, it’s just a game changer for making advanced and reusable custom widgets without using protoUI.

class MyWidgetClass extends JetView {
   config(config) {
        .... customize config
       return newConfig:
   }
}

export default class MyWidget extends MyWidgetClass {
    config() {
      return super.config({ .... my config }];
   }
}
#2

All is in the doc

export default class StandardView extends JetView {
  constructor(app, config){
    super(app, config);
    this._config = config;
  }
  config() {
    return {
      template:this._config.myTemplate
    }
  }
}