doc/crypto: include options and correct return type for setAAD()#21420
doc/crypto: include options and correct return type for setAAD()#21420ZaneHannanAU wants to merge 4 commits intonodejs:masterfrom ZaneHannanAU:patch-2
Conversation
doc/api/crypto.md
Outdated
| --> | ||
| - `buffer` {Buffer | TypedArray | DataView} | ||
| - Returns: {Cipher} for method chaining. | ||
| - `options` {Object} |
There was a problem hiding this comment.
It seems plaintextLength should be documented here as well, as a property of options, in a nested level.
There was a problem hiding this comment.
Yeah; I had originally planned on writing an AADOptions block but it was so short I didn't feel the need to.
Also I added CipherGCMOptions and CipherCCMOptions in @types/node; though not sure how I should go about that in @nodejs/node.
There was a problem hiding this comment.
If you check other documentations, you'll see how options are handled there. Normally it just get's a short description what it stands for right after the type.
|
cc @nodejs/crypto |
|
Hi @ZaneHannanAU! Welcome and thanks for the pull request! Note for whoever lands this change: The commit message should probably not use Something like that. |
|
So should we land or should we wait for |
|
@vsemozhetbyt added for now sorry |
doc/api/crypto.md
Outdated
| - `buffer` {Buffer} | ||
| - `options` {Object} | ||
| - `options` {Object} [`stream.transform` options][] | ||
| - `plaintextLength`: {nunmber} |
There was a problem hiding this comment.
Nit: delete colon and {nunmber} -> {number} so we can run the last CI)
doc/api/crypto.md
Outdated
| - `buffer` {Buffer | TypedArray | DataView} | ||
| - `options` {Object} | ||
| - `options` {Object} [`stream.transform` options][] | ||
| - `plaintextLength`: {nunmber} |
PR-URL: #21420 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Landed in c041fd2 |
PR-URL: #21420 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: James M Snell <jasnell@gmail.com>
Checklist
Ensure consistency within documentation.