| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
/cc @nodejs/documentation @nodejs/crypto |
Sorry, something went wrong.
|
Quick recheck: https://ci.nodejs.org/job/node-test-commit-linuxone/7934/ |
Sorry, something went wrong.
There was a problem hiding this comment.
Why was this changed to a more generic name?
Sorry, something went wrong.
There was a problem hiding this comment.
To sync with the docs - https://nodejs.org/api/crypto.html#crypto_hash_digest_encoding
Line 783 in 2e7ccc2
Sorry, something went wrong.
|
I'm not sure most of these changes are worth it. It's not necessary to ensure the documentation parameter names exactly match what are used internally. |
Sorry, something went wrong.
There was a problem hiding this comment.
options seemed like the better name here?
Sorry, something went wrong.
There was a problem hiding this comment.
Um … “binder”?
Elsewhere in the code we name these things makeFoo, so you could call it makeRSAMethod or so if you at set on wanting to change the names.
Sorry, something went wrong.
There was a problem hiding this comment.
This TypeError gets really weird now.
Also, if anything, engineID is probably better.
Sorry, something went wrong.
There was a problem hiding this comment.
I know, there is at least another place like this.
I'll do the migration to internal/errors and fix these.
Sorry, something went wrong.
The reasoning to synchronize is to help with debugging, where you are exposed the "internal" arguments' names. |
Sorry, something went wrong.
|
@refack It’s okay to break links in the documentation so long as it’s updated throughout our docs. |
Sorry, something went wrong.
It's more delicate work. I'll give it another look if there are places where it's obviously better to break the docs. Also it breaks "permalinks" that might be embedded in other sites, so the change should really be worth it and I'd even categorize it semver-major. |
Sorry, something went wrong.
There was a problem hiding this comment.
This change has to be done in the list below the paragraph. All the options are explained there.
Sorry, something went wrong.
| description: Support for RSASSA-PSS and additional options was added. | ||
| --> | ||
| - `privateKey` {string | Object} | ||
| - `key` {string} |
There was a problem hiding this comment.
Description of Object case in second paragraph L988
Sorry, something went wrong.
|
@mscdex @addaleax @thefourtheye addressed comments PTAL |
Sorry, something went wrong.
| added: v0.11.8 | ||
| --> | ||
| - `spkac` {string | Buffer | TypedArray | DataView} | ||
| - `encoding` {string} (Default `utf-8`) used to encode the `spkac` into a Buffer |
There was a problem hiding this comment.
For string literal values, single quotes should be added inside the backticks: `'utf-8'`
Sorry, something went wrong.
| added: v0.11.8 | ||
| --> | ||
| - `spkac` {string | Buffer | TypedArray | DataView} | ||
| - `encoding` {string} (Default `utf-8`) used to encode the `spkac` into a Buffer |
There was a problem hiding this comment.
Ditto
Sorry, something went wrong.
| added: v0.7.1 | ||
| --> | ||
| - `autoPadding` {boolean} Defaults to `true`. | ||
| - `autoPadding` {boolean} (Default `true`). |
There was a problem hiding this comment.
If we're going to switch these, we should do so consistently. There are other instances in this document.
Sorry, something went wrong.
|
My comment about changing the code still stands. |
Sorry, something went wrong.
There was a problem hiding this comment.
The doc changes LGTM but I would also prefer not to include the changes in crypto (besides the consolidation of the rsaPublic and rsaPrivate functions).
Sorry, something went wrong.
|
This needs a rebase. I think the doc changes could land soon otherwise. |
Sorry, something went wrong.
|
Closing due to long inactivity. @refack please feel free to reopen if you want to further pursue this! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes: #14800
Checklist
Affected core subsystem(s)
crypto,doc