This commit is a significant rewriting of client-side discuss, chatter, chat window, and messaging menu using OWL. The behavior should be broadly the same, with some slight functional changes here and there. From a technical standpoint, the code of messaging is mainly organized in 2 main groups of modules: - models, which are logical entities that depict the client-side state of messaging as a whole. - components, which are in charge of displaying information from models. This refactoring also introduces new JS guidelines regarding folder structure (/static) and naming rules for JS modules. Community PR: https://github.com/odoo/odoo/pull/39023 Enterprise PR: https://github.com/odoo/enterprise/pull/6249 Task-1914207 This PR is a collaborative work by Alexandre, Julien, Sébastien and Xavier, with the precious help of Lucas to speed it up towards the end. closes odoo/odoo#39023 Related: odoo/enterprise#6249 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com> Co-authored-by: Alexandre Kühn <aku@odoo.com> Co-authored-by: Julien Giannone <jgi@odoo.com> Co-authored-by: Lucas Perais <lpe@odoo.com> Co-authored-by: Sébastien Theys <seb@odoo.com> Co-authored-by: Xavier Dubuc <xdu@odoo.com>
The purpose is to have more common code for failure and notifications, with less override in `sms` and `snailmail`. task-2176017 closes odoo/odoo#44170 Related: odoo/enterprise#9140 Related: odoo/upgrade#918 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
Follow up on 4f5334a081ee0e551fc2848aa230dabc96984862 Before this commit, thread was not re-rendered correctly in Discuss App when user clicked on "Mark as Read" from Inbox and then changed conversation in a narrow time frame. This issue was discovered from a test that failed undeterministically on rare occasions (once every hundreds of builds on Runbot): ``` QUnit test failed: "mail > Discuss > all messages in "Inbox" in "History" after marked all as read" [message: "there should be 30 messages in History", actual: "0", expected: "30"] ``` This test crashed due to the rendering of Inbox after message fadeout animation that overwrote the rendering of History. As a result, thread widget indefinitely displays Inbox content, which is empty. The HTML content of Discuss during the crash shows that breadcrumb and discuss sidebar correctly have "History" as the active thread, but thread widget still shows "Inbox" as content: http://runbot.odoo.com/runbot/build/1092504 This commit fixes the issue by re-rendering of the thread with message fadeout animation only if the active thread has not changed. closes odoo/odoo#44585 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
Revision on https://github.com/odoo/odoo/commit/9a66619db33fca5f0cb81d9f6bfeb0fb0290cf68 Commit above improves the web client startup by not having to wait for discuss widgets to fully load beforehand. However, it introduced an issue with chatter when the 1st rendering happens before messaging becomes ready: it displays "Creating a record..." instead of the whole history of messages. This happens because when messaging is ready, it updates data from the chatter but it does not trigger a re-render. This commit fixes the issue by triggering a re-render on messaging ready. When messaging is not ready, thread field now displays "Loading..." instead of the message "Creating a record...". Task-Id 2078193 closes odoo/odoo#38751 X-original-commit: 93bdd7c91095025f4d6e7a058e0ab1c4e1a0ad60 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
Delete attachment from message makes only sense from chatter. Task-Id 2058455
closes odoo/odoo#32088 Signed-off-by: Christophe Simonis <chs@odoo.com>
closes odoo/odoo#31790 Signed-off-by: Christophe Simonis <chs@odoo.com>