Closed
Bug 1448334
Opened 6 years ago
Closed 5 years ago
"File a bug" link from file view to bugzilla
Categories
(Webtools :: Searchfox, enhancement)
Webtools
Searchfox
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jorendorff, Assigned: kats)
References
Details
In a discussion why BUG_COMPONENT exists in moz.build files: <jorendorff> looks like it was for this maybe? https://bugzilla.mozilla.org/show_bug.cgi?id=1352495 <jorendorff> never landed <jorendorff> maybe searchfox should have a "file a bug" link that autofills the component :D <freddyb> jorendorff: that'd be great. want to file an issue in searchfox repo? :) <jorendorff> i was kind of joking... And yet here we are.
Assignee | ||
Comment 1•6 years ago
|
||
Is this something people would actually use? While I do occasionally spot bugs in code while browsing on searchfox, I don't know if it happens frequently enough to warrant optimizing the flow of filing a bug.
Assignee | ||
Comment 2•6 years ago
|
||
If we did want to implement this, I think a reasonable approach would be to run something like: find . -type f -name "*.cpp" | xargs ./mach file-info bugzilla-component on the m-c tree, and turn the output into a .json file that contains a map from filename -> component. Then, when generating the html for the rendered file, we can look up the map to see if there's an associated component, and add a "File a bug" link under the "Source code" section of the floater nav thingy.
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → kats
Assignee | ||
Comment 3•5 years ago
|
||
https://github.com/mozsearch/mozsearch/pull/177
Assignee | ||
Comment 4•5 years ago
|
||
This is deployed now
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•