Skip to content
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

[ADD] mail_contact_type: #1264

Merged
merged 3 commits into from
Feb 22, 2024

Conversation

barkat-matthias
Copy link

Provides a method to use on mail templates to select contacts by their categories.

@barkat-matthias barkat-matthias force-pushed the 14.0-mail-contact-type-04122023 branch from a6ea5dd to 876ea51 Compare December 5, 2023 13:48
Copy link

@petrus-v petrus-v left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

mail_contact_type/models/res_partner.py Outdated Show resolved Hide resolved
mail_contact_type/models/mail_contact_type.py Show resolved Hide resolved
mail_contact_type/models/res_partner.py Outdated Show resolved Hide resolved
@barkat-matthias barkat-matthias force-pushed the 14.0-mail-contact-type-04122023 branch 3 times, most recently from e4307f2 to 8379a38 Compare December 6, 2023 09:11
@alexandregaldeano alexandregaldeano force-pushed the 14.0-mail-contact-type-04122023 branch 2 times, most recently from 1cbd2a5 to d97aef0 Compare December 6, 2023 14:20
name = super()._get_name()

if (
not self._context.get("show_mail_contact_types")
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alexandregaldeano, @barkat-matthias I can't see where this context is used in this module ?

I suppose we should add it in the mail composer (not the one from accounting to avoid extra dependency which should be take care by an other module.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petrus-v it's set here

@barkat-matthias barkat-matthias force-pushed the 14.0-mail-contact-type-04122023 branch from cd9f71c to a261bc7 Compare December 8, 2023 10:52
Provides a method to use on mail templates to select contacts by their categories.

---------

Co-authored-by: Pierre Verkest <[email protected]>
Co-authored-by: Alexandre Galdeano <[email protected]>
Co-authored-by: Matthias BARKAT <[email protected]>
@barkat-matthias barkat-matthias force-pushed the 14.0-mail-contact-type-04122023 branch from a261bc7 to 0e290a8 Compare December 8, 2023 10:54
Matthias BARKAT and others added 2 commits January 26, 2024 10:58
Copy link
Member

@hbrunn hbrunn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't see anything wrong with the code, but if I were to implement such a functionality I'd build on partner_multi_relation, add a code field to relation types and look at that code in contact_by_types/_name_search

name = super()._get_name()

if (
not self._context.get("show_mail_contact_types")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petrus-v it's set here

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@dreispt
Copy link
Member

dreispt commented Feb 22, 2024

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 14.0-ocabot-merge-pr-1264-by-dreispt-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 792a04f into OCA:14.0 Feb 22, 2024
7 checks passed
@OCA-git-bot
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants