Skip to content

doc: clarify agent.options is not part of public API - #62921

Open
rio767 wants to merge 1 commit into
nodejs:mainfrom
rio767:patch-1
Open

rio767 wants to merge 1 commit into
nodejs:mainfrom
rio767:patch-1

Conversation

@rio767

@rio767 rio767 commented Apr 24, 2026

Copy link
Copy Markdown

Adds a note clarifying that agent.options is not part of the public API and should not be relied upon.

Adds a note clarifying that agent.options is not part of the public API and should not be relied upon.
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/http
  • @nodejs/net

@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to Node.js documentation. http Issues and PRs related to the http subsystem. labels Apr 24, 2026

@Ethan-Arrowood Ethan-Arrowood left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I don't think this is needed. The collaborator guide specifies "All functionality in the official Node.js documentation is part of the public API." By literally documenting something that is meant to be ignored we are contradicting that rule.

So a couple other options:

  1. If this API is meant to be public; lets document it!
  2. If this API is mean to be private, but is publicly accessible, can we consider switching it to a private field? In Node.js we use symbols to achieve this; there is a plethora of example throughout the source to refer to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to Node.js documentation. http Issues and PRs related to the http subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants