Closed
Bug 640051
Opened 14 years ago
Closed 14 years ago
Align naming of stack-utils.js and dom_utils.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gmealer, Unassigned)
References
Details
(Whiteboard: [module-refactor])
We now have stack-utils.js and dom_utils.js. I'd prefer to standardize on either dash or underscore.
stack-utils.js claims its own name is stack_utils.js, so I suspect that's what should get renamed. OTOH, if Mozilla has a clear standard for how to do multiword file names, we should do that.
Re: multiword names in general, I personally try to avoid them.
If I have to go there I usually just run words together unless they're really unclear, but given a choice I'd standardize on dash. Underscore is often problematic because cursors and underlining (including linkification) obscure it.
I also try to avoid "utils" in names since it's a null word. By definition, anything in the file is a utility for whatever subject the file covers.
I'd personally have gone with collector.js (or nodecollector.js) and stack.js.
| Reporter | ||
Updated•14 years ago
|
Whiteboard: [module-refactor]
Comment 1•14 years ago
|
||
The node collector requires changes so I wouldn't take this module into account for the refactoring round now. But you are right in the general terms. We should rename stack-utils.js into stack.js and put it into a sub folder at the same time. This module is will only be used by 1 or 2 other modules and shouldn't be exposed at the top level module folder.
Comment 2•14 years ago
|
||
Oh and re '-' vs. '_'. You can't have a dash in the variable name.
| Reporter | ||
Comment 3•14 years ago
|
||
Good point, re: _ in identifiers.
Re: stack.js, anything private shouldn't be jsdoc'd as public then. I wouldn't bother jsdocing it at all, but if you do, make it @private.
I don't know that otherwise we need to hide the file in a subdir. The docs should be the guide as to what tests can use, not the directory structure. If you feel strongly we can hide it, though.
Comment 4•14 years ago
|
||
For now don't change any doc specification for stack.js, because at the moment test will partly of to use it. We will re-check the stack module in the refactoring round of milestone 2.
| Reporter | ||
Comment 5•14 years ago
|
||
Yeah, I won't change anything in there. But generally, I'd follow that guideline.
Seems like jsdoc does the right thing with _identifiers, as you found out, but other things we might need to explicitly mark @private if they're going to have jsdoc style comments. dom_utils is also throwing trash into the _global section, for example.
Comment 6•14 years ago
|
||
dom_utils needs an update in general. So I would cover that part later. What about naming both modules to stack.js and dom.js?
| Reporter | ||
Comment 7•14 years ago
|
||
Sure, sounds good.
| Reporter | ||
Comment 8•14 years ago
|
||
Fixed with patch in Bug 638967
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 9•14 years ago
|
||
A side note here. This change broke some of our existing module tests. Next time please run the tests to ensure we don't break anything. I will fix that shortly.
| Reporter | ||
Comment 10•14 years ago
|
||
Sorry about that. I thought I did run the tests, but I must have missed the modules/test one on this change. That's another reason to not have two separate test directories, so that I can just run tests once and know they passed. Let's discuss later.
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•