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

Dedupe selected fields, simplify, removed greeting id fields #29632

Merged
merged 1 commit into from
Mar 6, 2024

Conversation

eileenmcnaughton
Copy link
Contributor

@eileenmcnaughton eileenmcnaughton commented Mar 6, 2024

Overview

Dedupe selected fields, simplify, removed greeting id fields

Before

The code was previously shared with import & is super confusing + has some stuff that is really for import, not dedupe.

Functionally the 3 fields that hold greeting IDs don't make sense for dedupe - ie email_greeting_id, postal_greeting_id, addressee_id could only really have crept into dedupe fields because they make sense for importing.

e.g in this image 'Addressee' disappears from the list

image

After

I removed the 3 greeting id fields & the complex code that adds them, but otherwise no change to returned fields, but added test cover to lock the results of this function in

Technical Details

Comments

Copy link

civibot bot commented Mar 6, 2024

🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷

Introduction for new contributors...
  • If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
  • A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
  • A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
  • If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
  • Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
  • A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
  • To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
  • For more information about contributing, see CONTRIBUTING.md.
Quick links for reviewers...

➡️ Online demo of this PR 🔗

@civibot civibot bot added the master label Mar 6, 2024
Comment on lines +181 to +203
$contactTypeFields = [
'Organization' => [
'legal_name' => 'Legal Name',
'organization_name' => 'Organization Name',
'sic_code' => 'Sic Code',
],
'Individual' => [
'birth_date' => 'Birth Date',
'is_deceased' => 'Deceased',
'deceased_date' => 'Deceased Date',
'first_name' => 'First Name',
'formal_title' => 'Formal Title',
'gender_id' => 'Gender ID',
'prefix_id' => 'Individual Prefix',
'suffix_id' => 'Individual Suffix',
'job_title' => 'Job Title',
'last_name' => 'Last Name',
'middle_name' => 'Middle Name',
],
'Household' => [
'household_name' => 'Household Name',
],
];
Copy link
Member

Choose a reason for hiding this comment

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

This metadata already exists in DAO_Contact::getFields(). E.g. the household_name field has this:

'contactType' => 'Household',

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@colemanw yeah - but the point of hard-coding it in the test is to make sure it doesn't change at all & this is a static reference to id

Copy link
Member

Choose a reason for hiding this comment

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

Ok sure. As long as the live code is reading from the metadata. Is it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@colemanw yep - the live code is readying from DAO::import() but I want to switch it to reading from the api

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@colemanw the live code also does this #29631 - which is fortunately tested so I plan to deconstruct that

@colemanw colemanw merged commit 21d5bf0 into civicrm:master Mar 6, 2024
3 checks passed
@eileenmcnaughton eileenmcnaughton deleted the no_greeting_ids branch March 6, 2024 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants