Skip to content

Conversation

@thefourtheye
Copy link
Contributor

Checklist
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

doc, util

Description of change

improve util._extend function's documentation

@thefourtheyethefourtheye added util Issues and PRs related to the built-in util module. doc Issues and PRs related to the documentations. labels Aug 19, 2016
doc/api/util.md Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thefourtheye Do we need an example for deprecated function? its like warn users and teach them how to use it 😄

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True. But we have done that in log too

@cjihrig
Copy link
Contributor

Thanks for the PR, but I'm not sure that we should improve the docs for this function.

@cjihrig
Copy link
Contributor

Although maybe updating the function signature is appropriate :-)

@mscdex
Copy link
Contributor

-1 to all but the function signature change.

@jasnell
Copy link
Member

Given the deprecated status, I agree that we likely shouldn't extend the documentation on this.

@thefourtheye
Copy link
ContributorAuthor

Okay. Fixed the function signature alone now. Hope this is okay.

doc/api/util.md Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be origin and add to keep consistent with source, see https://github.com/nodejs/node/blob/master/lib/util.js#L976

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not util._extend(target, source) without obj suffix ? @yorkieorigin/add combination is confusing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both look good to me, but consistence should be considered here.

Copy link
Contributor

@princejwesleyprincejwesleyAug 20, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yorkie In the case of origin/add pair, I have code in place to understand what the particular function does. But documentation is the face of the code and we can not expect user to read the code in case of doubt. Its my humble opinion. ( extend the target from source)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@princejwesley Why do we not change the source to target/source, too?

@jasnell
Copy link
Member

LGTM

@thefourtheye
Copy link
ContributorAuthor

@yorkie@princejwesley Renamed the parameter names, for clarity. PTAL.

@targos
Copy link
Member

LGTM

@yorkie
Copy link
Contributor

LGTM :-)

@jasnell
Copy link
Member

@cjihrig and @mscdex ... PTAL

@mscdex
Copy link
Contributor

LGTM

@jasnell
Copy link
Member

@thefourtheye ... can you please rebase and update this?

@thefourtheyethefourtheyeforce-pushed the doc-fix-util-extend branch 2 times, most recently from 5e1a699 to 7aa1e22CompareAugust 24, 2016 04:53
@thefourtheye
Copy link
ContributorAuthor

@jasnell Done. I'll land this tomorrow, if there are no other suggestions.

The function signature of `util._extend` is not intuitive and the documentation doesn't specify the necessary second parameter. This patch changes the parameter names in the code and the function params in doc. PR-URL: nodejs#8187 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Yorkie Liu <[email protected]> Reviewed-By: Brian White <[email protected]>
@thefourtheye
Copy link
ContributorAuthor

Landed in b3e7ac2

@thefourtheyethefourtheye deleted the doc-fix-util-extend branch August 26, 2016 13:29
thefourtheye added a commit that referenced this pull request Aug 26, 2016
The function signature of `util._extend` is not intuitive and the documentation doesn't specify the necessary second parameter. This patch changes the parameter names in the code and the function params in doc. PR-URL: #8187 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Yorkie Liu <[email protected]> Reviewed-By: Brian White <[email protected]>
@Fishrock123Fishrock123 mentioned this pull request Sep 6, 2016
Fishrock123 pushed a commit to Fishrock123/node that referenced this pull request Sep 8, 2016
The function signature of `util._extend` is not intuitive and the documentation doesn't specify the necessary second parameter. This patch changes the parameter names in the code and the function params in doc. PR-URL: nodejs#8187 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Yorkie Liu <[email protected]> Reviewed-By: Brian White <[email protected]>
Fishrock123 pushed a commit that referenced this pull request Sep 9, 2016
The function signature of `util._extend` is not intuitive and the documentation doesn't specify the necessary second parameter. This patch changes the parameter names in the code and the function params in doc. PR-URL: #8187 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Yorkie Liu <[email protected]> Reviewed-By: Brian White <[email protected]>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docIssues and PRs related to the documentations.utilIssues and PRs related to the built-in util module.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

@thefourtheye@cjihrig@mscdex@jasnell@targos@yorkie@princejwesley@MylesBorins