summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/fields
diff options
context:
space:
mode:
authorLucas Perais (lpe) <lpe@odoo.com>2019-04-15 12:41:26 +0000
committerLucas Perais (lpe) <lpe@odoo.com>2019-04-15 12:41:26 +0000
commit7bf25cc333b0a3afc7e0a67f76f019407dba7e12 (patch)
tree52740b79fc85915e6467955e9a99a6d75d473403 /addons/web/static/src/js/fields
parent6a57ad66b8374966ba7011e34cec20f6344f4f6d (diff)
[FIX] web: search view handles JSON parsable domains
Before this commit, a domain that had been written in order to be JSON parsable, would trigger a JS crash when activated in the UI It happens when adding custom filters through the edition of the search view with studio This was because, Odoo developers write, in the XML of a search view domains python style: `[('field', '=', 'value')]` When parsing the view in JS, this doesn't get altered by `xml_to_json` Then, the search view code evaluates it python style This commit considers that behavior fortunate, but not really clear or conceptually correct But, when customizing a search view with studio, the domain is written by the code, in JS JSON parsable format `[["field", "=", "value"]]` This should be supported too, as so many customizations may have been done before hand After this commit, both expressions are supported by the filters menu OPW 1957297, 1960732, 1965649 (at least) closes odoo/odoo#32690 Signed-off-by: Lucas Perais (lpe) <lpe@odoo.com>
Diffstat (limited to 'addons/web/static/src/js/fields')
0 files changed, 0 insertions, 0 deletions