Closed Bug 1452061 Opened 7 years ago Closed 7 years ago

CamelCase all React component files in /devtools/client/performance/components/

Categories

(DevTools :: Performance Tools (Profiler/Timeline), enhancement, P3)

enhancement

Tracking

(firefox63 fixed)

RESOLVED FIXED
Firefox 63
Tracking Status
firefox63 --- fixed

People

(Reporter: jdescottes, Assigned: jdescottes)

References

Details

(Keywords: good-first-bug)

Attachments

(1 file, 1 obsolete file)

We recently agreed to name our React component file names using the CamelCase convention. However the files in /devtools/client/performance/components/ do not follow this convention, so let's rename them. This is an easy fix, but make sure you read the contribution docs before starting: http://docs.firefox-dev.tools/ so that you can build Firefox locally and verify that things still work after your change. After building, just running the built Firefox and opening the memory panel (by first enabling it from the settings panel) should be enough of a test that things still work.
Sorry for copy pasting a summary, I assumed the last part was just a set of generic instructions: "After building, just running the built Firefox and opening the memory panel (by first enabling it from the settings panel) should be enough of a test that things still work." Should be "After building, just running the built Firefox and opening the Performance panel (by first enabling it from the settings panel) should be enough of a test that things still work"
Just to let everyone know, I'm almost done with a patch for this issue. I'm just making some finishing touches.
Comment on attachment 8968485 [details] Bug 1452061 - renamed React component files in devtools/client/performance to be CamelCase. https://reviewboard.mozilla.org/r/237186/#review243150 Hey thanks for taking a stab at this. To clarify a bit, the intent was on `CamelCase` for the components, and not `camelCase`. Also, this review is confusing to look at, since it appears that all the files are deleted and then recreated. Mercurial has a nice built in command to let you rename files so that it understands when things have moved, and not been deleted: http://hgbook.red-bean.com/read/mercurial-in-daily-use.html#id364064 This would make the review a lot easier to look at. Thanks!
Attachment #8968485 - Flags: review?(gtatum) → review-
Hi there, I am a student at a University working with a team of 3 other students who are also gaining experience in Open Source. We thought that this bug would be a good first bug to get familiar with the Patch process. We are wondering if you could clarify what the React component files are in /devtools/client/performance/components/. Just want to make sure that to fix this, we simply need to rename the files, such as recording-button.js to RecordingButton.js. Any information you can give is much appreciated. Thank you!
Hey, I have another draft up. Unfortunately, though I wasn't able to replicate what you mentioned about renaming files. I tried using hg mv as stated in your link but it still displays the diff as a removal + addition.
Comment on attachment 8968485 [details] Bug 1452061 - renamed React component files in devtools/client/performance to be CamelCase. https://reviewboard.mozilla.org/r/237186/#review256286 Thanks for the patch but as Greg mentioned previously, we need to use `hg move` in order to preserve the source history and make the diff more readable.
Attachment #8968485 - Flags: review-
Product: Firefox → DevTools
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Comment on attachment 8985521 [details] Bug 1452061 - CamelCase all React component files in devtools performance panel; https://reviewboard.mozilla.org/r/251134/#review262498 Sorry the delay on the view, it all looks reasonable to me! Thanks!
Attachment #8985521 - Flags: review?(gtatum) → review+
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9162b1c01237 CamelCase all React component files in devtools performance panel;r=gregtatum
Backed out changeset 9162b1c01237 (bug 1452061) for failing at performance/components/test/test_jit_optimizations_01.html on a CLOSED TREE Backout link: https://hg.mozilla.org/integration/autoland/rev/e679e55fc5d485d52ce5893bb2cb5315a1839390 Push with failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=9162b1c012371b3bb2d2f941e9d54f38fc33f73e Log link: https://treeherder.mozilla.org/logviewer.html#?job_id=189783426&repo=autoland&lineNumber=5107 Log snippet: [task 2018-07-24T13:25:16.232Z] 13:25:16 INFO - SimpleTest START [task 2018-07-24T13:25:16.248Z] 13:25:16 INFO - TEST-START | devtools/client/performance/components/test/test_jit_optimizations_01.html [task 2018-07-24T13:25:16.332Z] 13:25:16 INFO - GECKO(3179) | ++DOMWINDOW == 22 (0xe3270400) [pid = 3179] [serial = 22] [outer = 0xe2df8d90] [task 2018-07-24T13:25:17.302Z] 13:25:17 INFO - GECKO(3179) | ++DOMWINDOW == 23 (0xe2df4400) [pid = 3179] [serial = 23] [outer = 0xe2df8d90] [task 2018-07-24T13:25:17.784Z] 13:25:17 INFO - TEST-INFO | started process screentopng [task 2018-07-24T13:25:18.352Z] 13:25:18 INFO - TEST-INFO | screentopng: exit 0 [task 2018-07-24T13:25:18.353Z] 13:25:18 INFO - TEST-UNEXPECTED-FAIL | devtools/client/performance/components/test/test_jit_optimizations_01.html | [SimpleTest.finish()] No checks actually run. (You need to call ok(), is(), or similar functions at least once. Make sure you use SimpleTest.waitForExplicitFinish() if you need it.) [task 2018-07-24T13:25:18.354Z] 13:25:18 INFO - afterCleanup@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:1187:13 [task 2018-07-24T13:25:18.355Z] 13:25:18 INFO - executeCleanupFunction@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:1221:13 [task 2018-07-24T13:25:18.357Z] 13:25:18 INFO - SimpleTest.finish@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:1240:5 [task 2018-07-24T13:25:18.359Z] 13:25:18 INFO - window.onload@chrome://mochitests/content/chrome/devtools/client/performance/components/test/test_jit_optimizations_01.html:64:5 [task 2018-07-24T13:25:18.360Z] 13:25:18 INFO - EventHandlerNonNull*@chrome://mochitests/content/chrome/devtools/client/performance/components/test/test_jit_optimizations_01.html:16:1
Flags: needinfo?(jdescottes)
Attachment #8968485 - Attachment is obsolete: true
Flags: needinfo?(jdescottes)
Attachment #8968485 - Flags: review?(gtatum)
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5cc1be9e8d14 CamelCase all React component files in devtools performance panel;r=gregtatum
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: