diff options
| author | Jairo Llopis <yajo.sk8@gmail.com> | 2017-03-21 11:06:21 +0100 |
|---|---|---|
| committer | Géry Debongnie <ged@odoo.com> | 2017-03-28 15:12:56 +0200 |
| commit | 5fc3979262c46217c0d566ddc1b1f3d47b9d69dc (patch) | |
| tree | 277025cf9e121cc5b2e442abc78cf555f81d150a /addons/web/static/src/js/framework/pyeval.js | |
| parent | 8e7f34c32304d8c0f48259fd956d64392ed1007f (diff) | |
[FIX] web: Avoid double-fetching many2many tags in list views
Before this patch, #15920 was happening. The problem was that calling `render_cell` produced a call to [`record.set(column.id + '__display', value)`][1], which triggers the `change` event, which called `render_record` the first time, which called again `render_cell` and produced the 2nd data fetch.
After this patch, `render_record` is only called if there is some place where to put the result, which does not happen in those situations.
There is still the problem that there is one call to name_get for each many2many widget found in a list view (instead of one per full view rendering), but at least they are not two calls!
[1]: https://github.com/odoo/odoo/blob/5d17749ff47c02294d5ff2ae56bbcef9d082562e/addons/web/static/src/js/view_list.js#L1125
Diffstat (limited to 'addons/web/static/src/js/framework/pyeval.js')
0 files changed, 0 insertions, 0 deletions