-
Notifications
You must be signed in to change notification settings - Fork 30.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: improve documentation on argument validation #56954
Open
Aditi-1400
wants to merge
1
commit into
nodejs:main
Choose a base branch
from
Aditi-1400:doc-update
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+62
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aduh95
reviewed
Feb 8, 2025
jasnell
reviewed
Feb 8, 2025
21efca9
to
3ee49f2
Compare
joyeecheung
approved these changes
Feb 11, 2025
UlisesGascon
approved these changes
Feb 12, 2025
Commit Queue failed- Loading data for nodejs/node/pull/56954 ✔ Done loading data for nodejs/node/pull/56954 ----------------------------------- PR info ------------------------------------ Title doc: improve documentation on argument validation (#56954) ⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile! Branch Aditi-1400:doc-update -> nodejs:main Labels c++, author ready, needs-ci Commits 1 - doc: improve documentation on argument validation Committers 1 - Aditi <[email protected]> PR-URL: https://github.com/nodejs/node/pull/56954 Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/56954 Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> -------------------------------------------------------------------------------- ℹ This PR was created on Fri, 07 Feb 2025 21:11:29 GMT ✔ Approvals: 2 ✔ - Joyee Cheung (@joyeecheung) (TSC): https://github.com/nodejs/node/pull/56954#pullrequestreview-2610220323 ✔ - Ulises Gascón (@UlisesGascon): https://github.com/nodejs/node/pull/56954#pullrequestreview-2611384161 ✔ Last GitHub CI successful ✘ No Jenkins CI runs detected -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncuhttps://github.com/nodejs/node/actions/runs/13293370008 |
Oh boy, somehow the CI checker in ncu wants Jenkins to be run for src/README.md changes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
c++
Issues and PRs that require attention from people who are familiar with C++.
needs-ci
PRs that need a full CI run.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the documentation to clearly explain the approach used for argument validation in Node.js,
with respect to public APIs and internal code.
It wasn't very clear to me while trying to validate the argument in #56942, thanks to @joyeecheung for providing the additional context that was missing from the documentation. :)