Open Bug 2011387 Opened 9 months ago Updated 5 months ago

[meta] Use proper private fields instead of _ prefixed properties in DevTools classes

Categories

(DevTools :: General, task, P3)

task

Tracking

(Not tracked)

People

(Reporter: nchevobbe, Unassigned)

References

(Blocks 4 open bugs)

Details

(Keywords: meta)

In a lot of classes, we're using _ prefixed property names to indicate that the property/method is private (see https://searchfox.org/firefox-main/search?q=this%5C._.*%5Cs%3D&path=devtools%2F&case=false&regexp=true)
We can now use proper private properties in Javascript, so we could migrate our codebase

Depends on: 1867722
Depends on: 1908669, 1877428
Depends on: 1876477
Depends on: 1742436, 1768150
Depends on: 1830010
Depends on: 2003846, 1960282
Depends on: 1977372
Priority: -- → P3

I can help with this while I'm in between other bugs. It'll be a good chance to practice the workflow.

Blocks: 2013442
Blocks: 2015237
Blocks: 2015238
Blocks: 2015239
Blocks: 2015240
Blocks: 2015241
Depends on: 2015821
Depends on: 2015837
Depends on: 2016041
Blocks: 2021639
Blocks: 2021645
Blocks: 2021644
Blocks: 2021643
Blocks: 2021642
Blocks: 2021641
Blocks: 2021640
Blocks: 2022400
Blocks: 2022402
Blocks: 2022403
Blocks: 2022404
Blocks: 2022405
Blocks: 2022406
Blocks: 2022407
Blocks: 2022408
Blocks: 2022409
Depends on: 2043637
Depends on: 2044311
You need to log in before you can comment on or make changes to this bug.