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

allow distinction to be made whether relationships are shown for user… #15811

Closed
wants to merge 1 commit into from

Conversation

yashodha
Copy link
Contributor

@yashodha yashodha commented Nov 11, 2019

… dashboard or relationship tab for hook usage

Overview

allow distinction to be made whether relationships are shown for user dashboard or relationship tab for hook usage

Comments

We could also add another parameter in the hook to indicate context but that would involve making changes to a commonly used hook signature.

… dashboard or relationship tab for hook usage
@civibot
Copy link

civibot bot commented Nov 11, 2019

(Standard links)

@civibot civibot bot added the master label Nov 11, 2019
@eileenmcnaughton
Copy link
Contributor

@mattwire I'm pretty sure this is the hook you wanted & I thought it was a bad idea because we'd be stuck with the horrible function forever if we added a hook - anyway now you own it - over to you to review this

@yashodha
Copy link
Contributor Author

@mattwire this is related to changes in #14184

@mattwire
Copy link
Contributor

mattwire commented Dec 4, 2019

@yashodha Can you add a code comment that explains why we are doing this (per explanation on the PR). Also can you add a PR to extend the documentation here: https://docs.civicrm.org/dev/en/latest/hooks/hook_civicrm_searchColumns/

Can you explain why you want to do this? As you can't differentiate the column headers are you wanting to display different information on the rows depending on which context is displaying?

@jaapjansma
Copy link
Contributor

Betty and I are reviewing PR's and we came across this one.

At December 4th, @mattwire requested to add documentation, @yashodha, were you able to do so and could you link the changes in this PR? If not are you still going to do this? As we do think the documentation is required.

@jaapjansma
Copy link
Contributor

Betty and I are reviewing PR's and we came across this one. @mattwire has asked some good questions and no answers has been given since then so we will close this PR as we don't see that this PR gets any follow up.

@jaapjansma jaapjansma closed this Mar 23, 2020
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