[16.0][FIX] mail_composer_cc_bcc: adapt to changes upstream

[hbrunn]

that's a nifty way to detect upstream changes and force adapting to it.

I wonder however if we couldn't achieve the same goal without copying so much code by setting some context keys that are picked up in an override of ir.mail.server#build_email

[OCA-git-bot]

Hi @hailangvn2023,
some modules you are maintaining are being modified, check this out!

[nilshamerlinck]

hi @hbrunn

• we took the occasion of the migration to 17.0 to get rid of this big override in [17.0][MIG] mail_composer_cc_bcc: Migration to 17.0 #1312
• iirc before that we had tried an approach based on context but failed, we'll look into it again

[trisdoan]

Hello @hbrunn, I just opened a PR: hbrunn#4 to add another changes from upstream, would you mind taking a look?

[hbrunn]

@trisdoan thanks, merged

[yajo]

Both the previous error message and the new changes are a bit cryptic... could you please explain what was happening?

[hbrunn]

@yajo they created a test that compares the hash of the source code of a function they override with a list of known hashes, so as soon as this changes in upstream, the test fails and we know we have to check if we need to incorporate any changes from there.

Added an error message to this effect in f2e9624

[yajo]

Ah wow! That was very non-obvious. Thanks.

Would you mind to squash it and put that explanation in the commit message itself? I think it'll be valuable some day when it happens again and we git blame over it.

Apart from that, the change LGTM.

[hbrunn]

added the commit message. But what do you want me to squash here? Seems like three logically independent changes to me

[yajo]

If the commits said something like "adapt to changes upstream. Changes in odoo/odoo#123123 made the hash change", their messages would be more valuable.

If a single commit contained all those explanation, that'd be equally good to me.

But in any case, it's OK if you don't prefer to squash. At this point it's good enough to me. 😄

Thank you very much!

/ocabot merge patch

[OCA-git-bot]

This PR looks fantastic, let's merge it!
Prepared branch 16.0-ocabot-merge-pr-1519-by-yajo-bump-patch, awaiting test results.

[OCA-git-bot]

Congratulations, your PR was merged at 695fc48. Thanks a lot for contributing to OCA. ❤️