Skip to content

Bug 1446236 - BugmailFilter: Divorce from Review extension#36

Open
CyberShadow wants to merge 3 commits intobugzilla:mainfrom
CyberShadow:bugmailfilter-wo-review
Open

Bug 1446236 - BugmailFilter: Divorce from Review extension#36
CyberShadow wants to merge 3 commits intobugzilla:mainfrom
CyberShadow:bugmailfilter-wo-review

Conversation

@CyberShadow
Copy link
Copy Markdown
Member

Don't include or process Mentor fields if the Review extension isn't loaded.

Comment thread extensions/BugmailFilter/Extension.pm Outdated
$rel_map[10] = !$rel_map[9];
$rel_map[11] = $bug->is_mentor($user);
$rel_map[12] = !$rel_map[11];
if (Bugzilla->have_extension('Review')) {
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Requires #35.

return \@relations;
}

use constant FILTER_RELATIONSHIPS => _gen_relations();
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Is this right?

@CyberShadow CyberShadow changed the title BugmailFilter: Divorce from Review extension Bug 1446236 - BugmailFilter: Divorce from Review extension Mar 31, 2018
Copy link
Copy Markdown
Member

@dylanwh dylanwh left a comment

Choose a reason for hiding this comment

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

needs to use has_extension

@CyberShadow CyberShadow force-pushed the bugmailfilter-wo-review branch from 65c0b7d to ca93f18 Compare June 7, 2020 23:03
@CyberShadow CyberShadow changed the base branch from unstable to master June 7, 2020 23:03
@CyberShadow
Copy link
Copy Markdown
Member Author

needs to use has_extension

@dylanwh Done, but... it seems that this and the other PRs were based on the unstable branch, which now seems abandoned. What is the way forward here, do I need to port the changes from unstable onto master or devel?

Base automatically changed from master to main February 13, 2021 18:03
Don't include or process Mentor fields if the Review extension isn't
loaded.
Calculating it eagerly is problematic as it would have to be done at
extension initialization, and we can't meaningfully query whether
other extensions are loaded during extension initialization.

Do it lazily and cache the result instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants