| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Why the passive->active change here? Is this a general rule we follow? I find if there are variables leaked into the global space less clear than if variables are leaked into the global space.
Sorry, something went wrong.
There was a problem hiding this comment.
How about if the test leaks variables into the global space?
The passive->active change is just following a general writing recommendation for increased clarity, but of course we should stick to passive voice if changing to active does not increase clarity. :-D
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM with nit
Sorry, something went wrong.
There was a problem hiding this comment.
4-seconds->4-second
Sorry, something went wrong.
There was a problem hiding this comment.
"include the common module, as the first executable statement" maybe?
Sorry, something went wrong.
There was a problem hiding this comment.
Or maybe to be really clear just say that the first two lines of the test must be:
'use strict';
const common = require('../common');or
'use strict';
require('../common');
Sorry, something went wrong.
There was a problem hiding this comment.
Generally, this holds good. But in some tests we have comments at the beginning (I mean before common) and that is also acceptable.
Sorry, something went wrong.
There was a problem hiding this comment.
Is there a reason we couldn't just standardise on what's in this guide?
'use strict';
require('../common');
// Comments after this
Sorry, something went wrong.
There was a problem hiding this comment.
If we did that we could lint for it.
Sorry, something went wrong.
There was a problem hiding this comment.
Lets see what @Trott thinks about it.
Sorry, something went wrong.
There was a problem hiding this comment.
How about include the common module before any other modules. as a reasonable concise compromise that we can expand on later if it is found to be inadequate?
Sorry, something went wrong.
|
Nits addressed, I think. |
Sorry, something went wrong.
* Remove passive voice * Remove unneeded modifiers * Minor comma change
* Remove passive voice * Remove unneeded modifiers * Minor comma change PR-URL: nodejs#10585 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Italo A. Casas <me@italoacasas.com>
* Remove passive voice * Remove unneeded modifiers * Minor comma change PR-URL: nodejs#10585 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Italo A. Casas <me@italoacasas.com>
* Remove passive voice * Remove unneeded modifiers * Minor comma change PR-URL: nodejs#10585 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Italo A. Casas <me@italoacasas.com>
* Remove passive voice * Remove unneeded modifiers * Minor comma change PR-URL: nodejs#10585 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Italo A. Casas <me@italoacasas.com>
* Remove passive voice * Remove unneeded modifiers * Minor comma change PR-URL: nodejs#10585 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Italo A. Casas <me@italoacasas.com>
* Remove passive voice * Remove unneeded modifiers * Minor comma change PR-URL: #10585 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Italo A. Casas <me@italoacasas.com>
* Remove passive voice * Remove unneeded modifiers * Minor comma change PR-URL: #10585 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Italo A. Casas <me@italoacasas.com>
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
doc test