Skip to content

doc: revise internal vs. public API in Collaborator Guide #24975

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.

Sign up for GitHub

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

Closed
Trott wants to merge 2 commits into from
Closed

doc: revise internal vs. public API in Collaborator Guide #24975

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3603497
doc: revise internal vs. public API in Collaborator Guide
Trott Dec 11, 2018
d0f9d52
fixup! doc: revise internal vs. public API in Collaborator Guide
Trott Dec 12, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
fixup! doc: revise internal vs. public API in Collaborator Guide
  • Loading branch information
@Trott
Trott committed Dec 12, 2018
commit d0f9d52b2a513d8eb2fa157a56d265ea3c6f420c
2 changes: 1 addition & 1 deletion COLLABORATOR_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,7 +218,7 @@ used in other CI test runs (such as `--worker`).
### Internal vs. Public API

All functionality in the official Node.js documentation is part of the public
API. Any undocumented object, property, method, argument, behavior, or even is
API. Any undocumented object, property, method, argument, behavior, or event is
internal. There are exceptions to this rule. Node.js users have come to rely on
some undocumented behaviors. Collaborators treat many of those undocumented
behaviors as public.
Expand Down