-
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: add missing options for crypto sign.sign() #22824
Conversation
CI-lite: https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/867/ сс @nodejs/crypto |
@@ -1121,6 +1121,8 @@ changes: | |||
* `privateKey` {string | Object} | |||
- `key` {string} | |||
- `passphrase` {string} | |||
- `padding` {integer} |
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.
I know it seems sensible to keep key
and passphrase
near each other, but I wonder if we would be best to alphabetize the options always. Especially in crypto
, the options lists can get long and having a clear and obvious ordering is helpful when you're looking for that one option you care about.
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.
Discussion: #22874
Fixes #22813
Checklist