New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IMP] mail: avoid broadcasting partner lists and tracking values #162065
base: master
Are you sure you want to change the base?
[IMP] mail: avoid broadcasting partner lists and tracking values #162065
Conversation
afb71f5
to
9b4818c
Compare
No task, no explanation ? Don't mark as ready when we cannot review. |
9b4818c
to
b9e7b61
Compare
@tde-banana-odoo I update the commit and the PR description to provide some context. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks ! Zboing !
bc5f485
to
41db430
Compare
41db430
to
893f6a3
Compare
a714fcc
to
81cad5d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR looks more code cleaning than anything.
I don't mind it, but as it is it introduces some disparity between _message_format_personalize
and _message_format(for_current_user)
.
It'd be nice to match the wording, and also they have similar concerns so would be also nice to improve locality by using similar LOCs. For example, _message_format_personalize
code could be moved into _message_format
and there's a parameter to personalise for given partners.
Before this PR, _message_format send all of the user that starred a message to the JS code. Since odoo#162065, this behaviour is not necessary anymore and a boolean can be used.
Before this PR, _message_format sent all of the users that starred a message to the JS code. Since odoo#162065, this behavior is not necessary anymore and a boolean can be used.
Before this PR, _message_format send all of the user that had a "need action" on a message to the JS code. Since odoo#162065, this behaviour is not necessary anymore and a boolean can be used.
Before this PR, `_message_format` sends all of the users that had a "need action" on a message to the JS code. Since odoo#162065, this behavior is not necessary anymore and a boolean can be used.
Before this PR, `_message_format` sent all of the users that starred a message to the JS code. Since odoo#162065, this behavior is not necessary anymore and a boolean can be used.
432d86c
to
7949d3e
Compare
Before this PR, `_message_format` function always included data that were only relevant to the logged user. It also `leak partner_ids`. This PR condition the `needaction_partner_ids`, `history_partner_ids`, `starredPersonas` and `trackingValues` values to a new param. This allows us to control when those data should be sent to the user. PR enterprise: odoo/enterprise#61353
7949d3e
to
44f86cf
Compare
Before this PR,
_message_format
function always included data that were onlyrelevant to the logged user. It also
leak partner_ids
.This PR condition the
needaction_partner_ids
,history_partner_ids
,starredPersonas
andtrackingValues
values to a new param.This allows us to control when those data should be sent to the user.
PR enterprise: https://github.com/odoo/enterprise/pull/61353