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

Remove unused method CRM_Contact_BAO_Contact_Utils::maxLocations #15091

Merged
merged 1 commit into from
Aug 21, 2019

Conversation

JKingsnorth
Copy link
Contributor

Overview

The \CRM_Contact_BAO_Contact_Utils::maxLocations method has no usages. I checked this using IDE tools and then by grepping the codebase for the 'maxLocations' string. I also tried grepping the commit log and didn't see any other references to it other than the declaration.

So let's remove it?

(The other option would be to deprecate it and remove it later...)

@civibot
Copy link

civibot bot commented Aug 21, 2019

(Standard links)

@civibot civibot bot added the master label Aug 21, 2019
@eileenmcnaughton
Copy link
Contributor

I agree

@eileenmcnaughton eileenmcnaughton merged commit 79c32ad into civicrm:master Aug 21, 2019
@mattwire
Copy link
Contributor

@agh1 @eileenmcnaughton It would be really helpful to capture interface changes/removals like this as a separate section on the release notes - so that an extension developer checking compatibility with versions for example can see at a glance that the function is no longer available for this version, same with deprecated functions we're removing and signature changes. I'm proposing a new tag that you could scrape along with the PRs?

@JKingsnorth
Copy link
Contributor Author

@mattwire Makes sense to me.

@agh1
Copy link
Contributor

agh1 commented Aug 21, 2019

@mattwire at the moment no tags are scraped, but it does seem reasonable if the tagging is consistent and can align well with a section of the release notes.

The bigger question is about the signal, noise, and effort involved in highlighting every change to a BAO method. We do have a flag at the top of the release notes if there is a change in the API, since there is an expectation that the API won't be changed lightly. On the other hand, using BAO and other methods directly is more explicitly at-your-own-risk, even though most of us do it at least occasionally.

I'm concerned that many of the changes in a release will alter the behavior, signature, and/or output of various functions, and even if @alifrumin and I had the time to highlight them all, we'd bury the other stuff in doing so.

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.

4 participants