summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic/basic_view.js
diff options
context:
space:
mode:
authorRaphael Collet <rco@odoo.com>2020-04-29 14:23:27 +0000
committerRaphael Collet <rco@odoo.com>2020-06-11 14:40:32 +0000
commitb15c2803699610179945ba690e1e5bc922a6e2b2 (patch)
tree13545d4244dc33b6ffe326ee797a936a17bf539c /addons/web/static/src/js/views/basic/basic_view.js
parent574dd61351f71dcc074b45523ca55ee1e59f8f75 (diff)
[FIX] core: update on new records should only recompute new records
The following situation can occur: a computed field depends on one2many lines, and during an onchange, a line is modified. Both the main record and the line are new records. If the many2one field is not in cache on the line, its value is fetched from the line's origin, and the field will be triggered for recomputation on the main record's origin instead of the record itself. The fix enforces the following property: if new records are modified, only new records can be triggered for recomputation. X-original-commit: f038b6c40b7045b6fe569c009d29ea092b614ed6
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_view.js')
0 files changed, 0 insertions, 0 deletions