Odoo Changelog — 2020-12-11

Friday, December 11, 2020

3 changes · master

Improvements(3)

Enhancements to existing features

[IMP] ir_ui_view: Refine error message

Enterprisemasterweb_ganttweb_studioMedium

Error reports shown during module installation or upgrades are now shorter and easier to act on when XML views are broken. Instead of overwhelming users with long internal tracebacks and full XML content, the message highlights the original problem, file location, and nearby lines needed to fix it.

Original PR description

When installing/upgrading a module with broken xml views, the module installation fails with an error message that should help the developer locate and correct the error. Before this commit, a…

When installing/upgrading a module with broken xml views, the module
installation fails with an error message that should help the developer
locate and correct the error.

Before this commit, a 3-level traceback was thrown at the developer:

1. The initial ValueError containing the original error message and some
   view context information.
2. The noisy re-cast of the ValueError to a ValidationError with no
   additionnal information.
3. An additionnal re-cast of the exception to add the original source
   file path plus the entire XML source code that failed to be parsed.

We argue the error contains too much noise as developers are mostly
interrested in correcting their erronous tag of their view, they are not
interrested in `ir_ui_view` internals.

The new exception report is much less talkative, the two tracebacks from
`ir_ui_view` are logged at the `DEBUG` level. The new exception still
contains the original error message with some context on the view record
and the original source file path but it only show 5 lines of XML around
the erronous tag.

Task: 2366612

#error-messages#module-upgrade#xml-views

Master helpdesk fsm kba

PR #12930

Enterprisemasterhelpdesk_fsmhelpdesk_fsm_reportMedium

Helpdesk teams can now create field service interventions in the right default project and automatically use the customer delivery address. Teams can also choose the correct worksheet when creating an intervention, helping field staff receive the right instructions and documentation.

#helpdesk#field service#worksheets

[IMP] web_gantt: mobile UI

PR #15209

Enterprisemasterplanningweb_ganttMedium

The Gantt view now displays more cleanly on small screens, with better scrolling and a simpler range selector. This makes planning schedules easier to review and navigate from mobile devices.

Original PR description

Before, gantt view on a small screen looks very weird.

Now, gantt view looks properly in a small screen with scrolling and
better range button UI with dropdown selection

Task ID: 2053857

#mobile#gantt#planning#user experience

When installing/upgrading a module with broken xml views, the module installation fails with an error message that should help the developer locate and correct the error. Before this commit, a 3-level traceback was thrown at the developer: 1. The initial ValueError containing the original error message and some view context information. 2. The noisy re-cast of the ValueError to a ValidationError with no additionnal information. 3. An additionnal re-cast of the exception to add the original source file path plus the entire XML source code that failed to be parsed. We argue the error contains too much noise as developers are mostly interrested in correcting their erronous tag of their view, they are not interrested in `ir_ui_view` internals. The new exception report is much less talkative, the two tracebacks from `ir_ui_view` are logged at the `DEBUG` level. The new exception still contains the original error message with some context on the view record and the original source file path but it only show 5 lines of XML around the erronous tag. Task: 2366612