-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
extensions/BugModal: Enable bugzilla-readable-status unconditionally #74
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove the if (1) { ... }
wrapping, that's not needed. I agree with this change other than this small nit.
I see no downside for enabling it always, and let it generate readable descriptions for the "Tracking" section. They appear useful even without the TrackingFlags extension.
8bf4d43
to
55ae989
Compare
Done :) |
Do we have a Bugzilla bug that goes with this PR? |
Still don't see a bug filed to go with this. |
Sorry, this is part of the BMO cleanup effort, so same bug as most other PRs from me. |
My understanding was that this was never an option, as the BMO team is uninterested in collaborating with any upstream. Has this changed? |
Yeah, I guess that's pretty much the way it is. They can cherry-pick if they want our stuff. And we'll do the same to theirs in the future. |
OK, so bug 1446236 |
FYI, this commit broke filing new bugs. |
correction, it broke show_bug, not filing new ones. |
This appears to have been missing from the patch: (I made this up based on the usage, but it seems to work) diff --git a/Bugzilla.pm b/Bugzilla.pm
index e58d84f32..06aa3fb0a 100644
--- a/Bugzilla.pm
+++ b/Bugzilla.pm
@@ -135,6 +135,12 @@ sub extensions {
return $extensions;
}
+sub has_extension {
+ my (undef, $extension) = @_;
+ return 1 if (grep { $_ eq $extension } Bugzilla->extensions);
+ return 0;
+}
+
sub cgi {
return request_cache->{cgi} ||= Bugzilla::CGI->new;
} However, that leads to:
I don't think this was ready to land. |
I see no downside for enabling it always, and let it generate readable descriptions for the "Tracking" section. They appear useful even without the TrackingFlags extension.
This also removes some hard-coded BMO/Firefox-specific logic.