-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: apply consistent styling for functions #4974
Conversation
Always refer to (for example) `assert.deepEqual()` as `assert.deepEqual()` and never as `assert.deepEqual`.
LGTM. |
@@ -89,7 +89,7 @@ parameter is undefined, a default error message is assigned. | |||
|
|||
## assert.deepStrictEqual(actual, expected[, message]) | |||
|
|||
Generally identical to `assert.deepEqual` with the exception that primitive | |||
Generally identical to `assert.deepEqual()` with the exception that primitive |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick, but shouldn't that also be a link (i.e. [
assert.deepEqual()][]
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will fix that!
Looks good. I'm planning on submitting a more comprehensive PR that fixes all such cases in the API documentation, but for now this can go in. |
Awesome. LGTM. I am on Mobile. I couldn't check all the places in this file. Hope you took care of all of them |
LGTM |
Just added one minor change to this at the suggestion of @benjamingr. @thefourtheye and/or @Qard: Can you check the minor update and confirm that it still looks good to you? |
Yep, LGTM. 👍 |
Always refer to (for example) `assert.deepEqual()` as `assert.deepEqual()` and never as `assert.deepEqual`. PR-URL: nodejs#4974 Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Stephen Belanger <[email protected]>
Landed in 3874f32 |
Always refer to (for example) `assert.deepEqual()` as `assert.deepEqual()` and never as `assert.deepEqual`. PR-URL: #4974 Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Stephen Belanger <[email protected]>
blocked by e436272 |
@thealphanerd can I help there? |
@eljefedelrodeodeljefe not just yet. That commit itself is blocked by another one. |
Always refer to (for example) `assert.deepEqual()` as `assert.deepEqual()` and never as `assert.deepEqual`. PR-URL: #4974 Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Stephen Belanger <[email protected]>
Always refer to (for example) `assert.deepEqual()` as `assert.deepEqual()` and never as `assert.deepEqual`. PR-URL: #4974 Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Stephen Belanger <[email protected]>
Always refer to (for example) `assert.deepEqual()` as `assert.deepEqual()` and never as `assert.deepEqual`. PR-URL: #4974 Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Stephen Belanger <[email protected]>
Always refer to (for example) `assert.deepEqual()` as `assert.deepEqual()` and never as `assert.deepEqual`. PR-URL: nodejs#4974 Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Stephen Belanger <[email protected]>
Always refer to (for example)
assert.deepEqual()
asassert.deepEqual()
and never asassert.deepEqual
./cc @nodejs/documentation @thefourtheye