Odoo/addons/mail/static/src/model/model_field_command.js, branch 14.0 The current checkout of upstream Odoo [FIX] mail: functions for FieldCommand should return boolean value 2021-02-23T07:36:23+00:00 Qiuyu (QHO) qho@odoo.com 2021-02-22T15:42:06+00:00 a3f5d0b292361a4aa3af8e7662f74150c5d85254 The executing function for FieldCommand should return boolean value to indicate whether the value changed for triggering the re-computation. closes odoo/odoo#66648 Signed-off-by: Sébastien Theys (seb) <seb@odoo.com> 
The executing function for FieldCommand should return boolean value
to indicate whether the value changed for triggering the re-computation.

closes odoo/odoo#66648

Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>
[FIX] mail: make Inbox counters more reliable in mark as read flows 2021-01-28T10:55:58+00:00 Sébastien Theys seb@odoo.com 2021-01-28T10:55:58+00:00 fa398ea291a72fa7752d382f85e6ef2ce7ac4c70 - Send the new Inbox counter when marking as read, to guarantee the JS has the correct value (instead of having to guess it which was impossible when an arbitrary domain was given to the method). NOTE: Manual increment is kept on receiving a new Inbox message because that one was reliable and it would have been more tricky to compute the new counter for each target partner (mark as read is one user doing an action for himself, whereas new message is from another user to potentially many different users). Generic counter for threads is also not sent on every change for similar reasons. - Refresh Inbox automatically when some messages are marked as read and there are more message on the server than currently loaded. - Remove confusing (and impossible to maintain) counter on non-origin threads (in particular channel followers). This behavior in JS was not consistent with the server which always counted only origin thread (model/res_id). task-2446302 closes odoo/odoo#65161 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com> 
- Send the new Inbox counter when marking as read, to guarantee the JS has the
  correct value (instead of having to guess it which was impossible when an
  arbitrary domain was given to the method).

  NOTE: Manual increment is kept on receiving a new Inbox message because that
  one was reliable and it would have been more tricky to compute the new counter
  for each target partner (mark as read is one user doing an action for himself,
  whereas new message is from another user to potentially many different users).
  Generic counter for threads is also not sent on every change for similar
  reasons.

- Refresh Inbox automatically when some messages are marked as read and there
  are more message on the server than currently loaded.

- Remove confusing (and impossible to maintain) counter on non-origin threads
  (in particular channel followers). This behavior in JS was not consistent with
  the server which always counted only origin thread (model/res_id).

task-2446302

closes odoo/odoo#65161

Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
[FIX] mail: ignore `undefined` in JS fields create/write 2020-09-23T09:52:30+00:00 Sébastien Theys seb@odoo.com 2020-09-22T16:25:24+00:00 f6e67650e8cb1f8f0be9e90dbaccf45692816c3e Passing a field containing `undefined` should lead to the same result as not passing the field. Fields that relied on `undefined` as a value have been changed to use the newly introduced `clear` command, that resets a field to its default value (often that is equal to `undefined`). task-2336491 closes odoo/odoo#58308 X-original-commit: b18824485483564d2ab80f41914a3548aa528ae0 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com> 
Passing a field containing `undefined` should lead to the same result as not
passing the field.

Fields that relied on `undefined` as a value have been changed to use the newly
introduced `clear` command, that resets a field to its default value (often
that is equal to `undefined`).

task-2336491

closes odoo/odoo#58308

X-original-commit: b18824485483564d2ab80f41914a3548aa528ae0
Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>