Closed Bug 1715822 Opened 3 years ago Closed 3 years ago

Rename references to resultBuckets to resultGroups

Categories

(Firefox :: Address Bar, task, P1)

task
Points:
3

Tracking

()

RESOLVED FIXED
95 Branch
Tracking Status
firefox94 + fixed
firefox95 --- fixed

People

(Reporter: bugzilla, Assigned: lesore0789, Mentored)

References

Details

(Keywords: good-first-bug, Whiteboard: [lang=js])

Attachments

(1 file, 2 obsolete files)

Bug 1715484 renamed the pref browser.urlbar.resultBuckets to browser.urlbar.resultGroups. However, there are still references to result buckets throughout Firefox. Those should be turned into references to result groups. These SearchFox queries are good places to start looking.

https://searchfox.org/mozilla-central/search?q=resultBucket&path=

https://searchfox.org/mozilla-central/search?q=buckets&path=urlbar&case=false&regexp=false

Hello,
May i work on this one as my first contribution?

Attached patch diff of browser folder (obsolete) — Splinter Review

Thank you for volunteering! Could you please post your patch on Phabricator? You can follow the instructions in this guide to do that. You also missed references to result buckets. Check the queries I posted in comment 0 for a reference to all the places you need to look, like test files and toolkit/components/places/UnifiedComplete.jsm. Do not modify the files in the security folder, as those are unrelated.

Assignee: nobody → akritidm

Should i change all "bucket(s)" references in the urlbar directory? I decided to change only the resultBucket(s) references as to not mess anything up.

Oh ok, now i see my attached diff does not show all of my changes. I'm working on posting with Phabricator.

(In reply to akritidm from comment #4)

Should i change all "bucket(s)" references in the urlbar directory? I decided to change only the resultBucket(s) references as to not mess anything up.

Yes, all references should be updated as far as I know. If I notice any that shouldn't be, I'll point them out in review.

Sorry for asking here, i didnt know how to contact you. How and when can i remove the telemetry.rst.orig?

(In reply to akritidm from comment #8)

Sorry for asking here, i didnt know how to contact you. How and when can i remove the telemetry.rst.orig?

hg remove browser/components/urlbar/docs/telemetry.rst.orig should do it.

I did the hg remove, then hg commit and moz-phab. I have a previous commit pilled up with this one. This is the output im getting:

Starting up..
Checking connection to Phabricator.
Looking for commits..
Loading commits..
Submitting 3 commits as Work In Progress
Loading existing revisions...
Loading diffs...
(    New) 583824:3456ca351c5d Removed telemetry.rst.orig
!! Missing Bug ID
!! Missing reviewers
   It will be submitted as "Changes Planned".
   Run submit again with --no-wip to prevent this.
(    New) 583823:155ada26b0fd Removed telemetry.rst.orig
!! Missing Bug ID
!! Missing reviewers
   It will be submitted as "Changes Planned".
   Run submit again with --no-wip to prevent this.
Figuring out who you are...
(D118406) 583822:78bee6008bf0 Bug 1715822
 * This revision has not changed and will not be submitted.
Checking commits..
Unable to submit commits:

583823:155ada26b0fd Removed telemetry.rst.orig
- missing bug-id

583824:3456ca351c5d Removed telemetry.rst.orig
- missing bug-id

Would appreciate some help at this point.

When writing commit messages for Firefox bugs, they should take the format

Bug <Bug number> - <Commit message>. r?<reviewer name>

So for this bug, it would be

Bug 1715822 - Replaced references to result buckets with result groups. r?harry

Renaming your commit should resolve the issues with moz-phab. Also please squash all commits together. You can do this with hg histedit. You don't need a separate commit for removing telemetry.rst.orig.

Attachment #9228206 - Attachment description: WIP: Bug 1715822 → Bug 1715822 - Replaced references to result buckets with result groups. r?harry

akritidm, are you still interested in working on this? Your patch was nearly complete.

Flags: needinfo?(akritidm)

I intend on finishing this. Been caught up with some other stuff lately and couldnt find the time to complete it.

Flags: needinfo?(akritidm)

Could you please finish this patch by the end of the week? Otherwise, I'll take it over to finish up the last touches and land it.

Flags: needinfo?(akritidm)

Clearing assignee so someone else can pick this up. akritidm, you're still free to pick this back up if you wish.

Assignee: akritidm → nobody
Whiteboard: [lang=js]

Hi Harry, my name is Leslie and I am an Outreachy applicant and I'd like to work on this bug. Can I be assigned to it?

Flags: needinfo?(htwyford)

Hello, I'm an Outreachy Applicant, can I just continue on with the work Harry was doing and submit a push request? Or do I need to be assigned first?

(In reply to Makenzie from comment #17)

Hello, I'm an Outreachy Applicant, can I just continue on with the work Harry was doing and submit a push request? Or do I need to be assigned first?

Sorry I just realized that Harry, you're the reporter, woops. Anyways, this looks like a great first bug for me and I'd love to contribute.

Thanks for all the interest! Makenzie, I'll let Leslie make a first attempt at this bug since she asked first. Leslie, the first step to fixing this bug is setting up your Firefox dev environment. Once you're set up, install the MozPhab command line tool:

./mach install-moz-phab

You can install the unfinished patch locally with moz-phab patch D118406 --apply-to central. That will apply the patch to the central branch of Firefox. Once you're done with the patch, you can push it for review just by running moz-phab. It will probably give you a message about how the revision already belongs to someone else. You can just confirm that you want to take it over. If it doesn't let you, try going to the patch's Phabricator page, scrolling to the bottom and selecting "Commandeer Revision". Then try again from the command line. If that still doesn't work, please needinfo me again.

Flags: needinfo?(htwyford)
Flags: needinfo?(akritidm)
Assignee: nobody → lesore0789
Status: NEW → ASSIGNED
Pushed by htwyford@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8652d1a2a2fa
Rename references from resultBuckets to resultGroups. r=harry
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 95 Branch
Flags: qe-verify-
Flags: in-testsuite+
Attachment #9228206 - Attachment is obsolete: true
Attachment #9228029 - Attachment is obsolete: true

[Tracking Requested - why for this release]: We need this for the Firefox Suggest preferences redesign targeting 95/94.

Comment on attachment 9245674 [details]
Bug 1715822 - Rename references from resultBuckets to resultGroups. r?harry

Beta/Release Uplift Approval Request

  • User impact if declined: We need this for the Firefox Suggest preferences redesign targeting 95/94.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: Please see uplift spreadsheet: https://docs.google.com/spreadsheets/d/1LavihS-VOPFYEyum7mrx6FKXmuQeHi9xQHfGNSxjnoY/edit?usp=sharing
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): This revision only changes the names of some variables and other identifiers in the code. There are no user-facing changes. All this code is covered by automated tests.
  • String changes made/needed:
Attachment #9245674 - Flags: approval-mozilla-release?

Comment on attachment 9245674 [details]
Bug 1715822 - Rename references from resultBuckets to resultGroups. r?harry

Approved for 94.0.2.

Attachment #9245674 - Flags: approval-mozilla-release? → approval-mozilla-release+

Changing the priority to p1 as the bug is tracked by a release manager for the current release.
See What Do You Triage for more information

Priority: P3 → P1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: