[FIX] web: fields set in fieldDependencies should have their "options" set

Bug brought by f45edfb

Before this commit, the debug manager crashed when clicking on "set defaults" on a view fetching a fieldDependency.
This was because the "options" key on the field was not set when the field originated from the fieldDependency of a widget.

After this commit, the data_manager ensures that key is present

OPW 780071

closes #20730
This commit is contained in:
Lucas Perais (lpe)
2017-11-08 10:21:32 +01:00
parent 0f638b3c63
commit 324d4bfb56
@@ -407,7 +407,7 @@ return core.Class.extend({
var deps = fieldsInfo[node.attrs.name].fieldDependencies;
for (var dependency_name in deps) {
if (!(dependency_name in fieldsInfo)) {
fieldsInfo[dependency_name] = {'name': dependency_name, 'type': deps[dependency_name].type};
fieldsInfo[dependency_name] = {'name': dependency_name, 'type': deps[dependency_name].type, 'options': deps[dependency_name].options || {}};
}
}
}