Uh oh!
There was an error while loading. Please reload this page.
test: clarify role of domains in microtask queue tests - #4474
Conversation
jasnell
commented
Dec 30, 2015
misterdjules
commented
Dec 30, 2015
Requiring domains calls So these tests test the Thus I would think we don't want to remove them. |
jasnell
commented
Dec 30, 2015
+1 to @misterdjules comments. However, it might be a good idea to add some comments into the test files themselves that explain so that the |
Trott
commented
Dec 30, 2015
Would it be OK to change the relevant lines from this: To just this?: (Along with adding a comment per @jasnell.) If so, I'll go ahead and do that (unless someone else is very motivated to do it). |
misterdjules
commented
Dec 31, 2015
Trott
commented
Dec 31, 2015
Rebased, updated, force pushed, changed description and title here. PTAL. |
cjihrig
commented
Dec 31, 2015
LGTM |
There was a problem hiding this comment.
Not very important, but just an observation: I would remove the calls _setupDomainUse part and just keep the changes the function that is used to call callbacks.... The reason is that that much details is not needed, and it would make the comment depend too much on implementation.
misterdjules
commented
Dec 31, 2015
I would personally rephrase it to something like: It depends a bit less on implementation details while still being explicit and clear. But I'm also fine with the existing comments, as long as the typo that I mentioned in an inline comment is fixed. |
Trott
commented
Dec 31, 2015
@misterdjules Updated with your definitely-better suggested text. Thanks. |
misterdjules
commented
Dec 31, 2015
The two commits will need to be squashed into one. The commit message can probably be shorter and just mention that a comment was added to make the purpose of these tests clearer. I don't think we need to quote the whole comment. Other than that, LGTM. Thank you very much for doing that! |
Add a comment to clarify how the tests work and their purpose. Also removes unnecessary assignment of domain module to a variable. PR-URL: nodejs#4474 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Julien Gilli <jgilli@fastmail.fm>
Add a comment to clarify how the tests work and their purpose. Also removes unnecessary assignment of domain module to a variable. PR-URL: nodejs#4474 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Julien Gilli <jgilli@fastmail.fm>
Trott
commented
Jan 2, 2016
Landed in b16a50d |
Add a comment to clarify how the tests work and their purpose. Also removes unnecessary assignment of domain module to a variable. PR-URL: nodejs#4474 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Julien Gilli <jgilli@fastmail.fm>
Add a comment to clarify how the tests work and their purpose. Also removes unnecessary assignment of domain module to a variable. PR-URL: #4474 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Julien Gilli <jgilli@fastmail.fm>
Add a comment to clarify how the tests work and their purpose. Also removes unnecessary assignment of domain module to a variable. PR-URL: #4474 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Julien Gilli <jgilli@fastmail.fm>
Add a comment to clarify how the tests work and their purpose. Also removes unnecessary assignment of domain module to a variable. PR-URL: nodejs#4474 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Julien Gilli <jgilli@fastmail.fm>
Add this comment:
Also removes unnecessary assignment of domain module to a variable.
R: @misterdjules
R: @jasnell