From 324d4bfb562a1549f4895fd7d8925a3353edb704 Mon Sep 17 00:00:00 2001 From: "Lucas Perais (lpe)" Date: Mon, 6 Nov 2017 16:49:10 +0100 Subject: [PATCH] [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 --- addons/web/static/src/js/services/data_manager.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/addons/web/static/src/js/services/data_manager.js b/addons/web/static/src/js/services/data_manager.js index 7e938770ba3..67e39d10bc8 100644 --- a/addons/web/static/src/js/services/data_manager.js +++ b/addons/web/static/src/js/services/data_manager.js @@ -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 || {}}; } } }