odoo/o-spreadsheet#7829
Created by fw-bot
Merged
at adc447278643c64930b542f55a5472e3c0e804c8
Statuses:
- label
- odoo:master-17.0-fix-action-children-order-rar-492463-fw
- head
- 21301be5701af37f900cf16d8b3ed7b136f03a82
- merged
- 3 weeks ago by BI, Rémi Rahir (rar)
| odoo/o-spreadsheet | |
|---|---|
| 17.0 | #7708 |
| 18.0 | #7817 |
| saas-18.2 | #7820 |
| saas-18.3 | #7822 |
| saas-18.4 | #7823 |
| 19.0 | #7827 |
| saas-19.1 | #7828 |
| master | #7829 |
[FIX] Actions: ensure the sequence is applied on action children
Currently, the helper 'createActions' pre-sorts a list of menuRegistry entries but this sort is not applied to the children (which can be generated dynamically). It never showed up as we rarely add children entries from different sources and their sequence often matches the order of insertion in the registry.
Description:
description of this task, what is implemented and why it is implemented that way.
Task: 5452669
review checklist
- [ ] feature is organized in plugin, or UI components
- [ ] support of duplicate sheet (deep copy)
- [ ] in model/core: ranges are Range object, and can be adapted (adaptRanges)
- [ ] in model/UI: ranges are strings (to show the user)
- [ ] undo-able commands (uses this.history.update)
- [ ] multiuser-able commands (has inverse commands and transformations where needed)
- [ ] new/updated/removed commands are documented
- [ ] exportable in excel
- [ ] translations (_t("qmsdf %s", abc))
- [ ] unit tested
- [ ] clean commented code
- [ ] track breaking changes
- [ ] doc is rebuild (npm run doc)
- [ ] status is correct in Odoo