the other one _should_ not be problematic, as field-container itself
isn't picked up as a "real" field itself, but we might bind to that
somewhere, where enabling could break this.
The editable one seems to not be used yet, according to Dominik, so
fix that now already.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
getEditable: function() {
let me = this;
let vm = me.getViewModel();
- vm.get('editable');
+ return vm.get('editable');
},
setValue: function(value) {
getValue: function() {
let me = this;
let vm = me.getViewModel();
+ // FIXME: add return, but check all use-sites for regressions then
vm.get('value');
},