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

Deprecate dupeQuery hook #29544

Merged
merged 2 commits into from
Mar 1, 2024

Conversation

eileenmcnaughton
Copy link
Contributor

Overview

Deprecte dupeQuery hook

Before

hook unused in universe & pretty fugly but no active discouragement

After

Marked deprecated - will do the same in docs

Technical Details

I did a universe search & found no usages - this hook feels to me like one of those things that got added cos it seemed like a good idea but was never really the right thing in the right place & not that useful. Let's deprecated it here & in the docs
& not encourage people to use it

Comments

I did a universe search & found no usages - this hook feels to me
like one of those things that got added cos it seemed like a good idea
but was never really the right thing in the right place & not that
useful. Let's deprecated it here & in the docs
& not encourage people to use it
Copy link

civibot bot commented Feb 29, 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 Feb 29, 2024
@eileenmcnaughton eileenmcnaughton changed the title Deprecte dupeQuery hook Deprecate dupeQuery hook Feb 29, 2024
@colemanw colemanw added the merge ready PR will be merged after a few days if there are no objections label Mar 1, 2024
@colemanw
Copy link
Member

colemanw commented Mar 1, 2024

@eileenmcnaughton 👍 I just pushed a noisy deprecation notice into this PR as well.

@eileenmcnaughton
Copy link
Contributor Author

test this please

@eileenmcnaughton
Copy link
Contributor Author

Thanks @colemanw - I had been thinking we should add something like invokeDeprecated() that would check if a hook is implemented - not just if it does anything - but this is still better with the deprecation

@eileenmcnaughton
Copy link
Contributor Author

unrelated fail

@eileenmcnaughton eileenmcnaughton merged commit 1881b0b into civicrm:master Mar 1, 2024
2 of 3 checks passed
@eileenmcnaughton eileenmcnaughton deleted the dedupe_query branch March 1, 2024 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
master merge on pass merge ready PR will be merged after a few days if there are no objections
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants