diff options
| author | Aaron Bohy <aab@odoo.com> | 2018-01-22 10:17:40 +0100 |
|---|---|---|
| committer | Aaron Bohy <aab@odoo.com> | 2018-01-22 19:59:23 +0100 |
| commit | f68ad51520150cd721814555b9e025da310204eb (patch) | |
| tree | 201c8078fe3e5b4b637cc6e78636636f502bdae9 /addons/web/static/src/js/views/basic/basic_renderer.js | |
| parent | 16c6b520fb901491e09cd3b86ac5b49171014892 (diff) | |
[FIX] web: honor action's groupBy on reload
Let's assume an action with a 'group_by' specified in its context.
Unless another groupby is specified in the search view, the action
groupby must be used. For list views, it was only working for the
first rendering of the view. As soon as it was reloaded, the action
groupby was lost.
For instance, go to Project, click on a project in the dashboard
[the action has 'group_by': 'stage_id' in its context], switch to
list view [the list is correctly grouped by 'stage_id'], reload by
clicking on the view switcher -> the view isn't grouped anymore.
It was actually working by chance on other views because they have
specific handling of the groupby (e.g. the kanban view allows the
attribute 'default_group_by' on its arch), but by default, the
action groupby must always be used at each load/reload if there is
no other groupby specified.
This rev. restores the behavior of saas-15, before the new views.
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_renderer.js')
0 files changed, 0 insertions, 0 deletions
