doc: clarify behavior of byteLength with 'base64' #11238
Conversation
nodejs-github-bot
added
buffer
doc/api/buffer.md
Outdated
There was a problem hiding this comment.
For consistency, please s/_Note_/*Note*:
There was a problem hiding this comment.
This isn’t specific to base64, it applies at least to hex, too:
> Buffer.byteLength('aa ', 'hex')
2
> Buffer.from('aa ', 'hex').length
1(I think it’s only those two encodings but I didn’t double-check.)
There was a problem hiding this comment.
@addaleax oh indeed. That makes wording it a bit more complicated...
doc/api/buffer.md
Outdated
doc/api/buffer.md
Outdated
There was a problem hiding this comment.
nit: Maybe mention that the method doesn’t account for whitespace in the input … for some people that might be included in “invalid”, but that’s kind of subjective…
|
Done, but now I have trouble coming up with a descriptive commit message. Any better suggestions? |
|
|
||
| *Note* that for `'base64'` and `'hex'`, this function assumes valid input. For | ||
| strings that contain non-Base64/Hex-encoded data (e.g. whitespace), the return | ||
| value might be greater than the length of a `Buffer` created from the string. |
There was a problem hiding this comment.
The return value could be smaller too (e.g. Buffer.byteLength('1345 4 ', 'hex') === 3, Buffer.from('1345 4 ').byteLength === 7), but then since the data is invalid it's just hard to say. Maybe just say something like the return value is meaningless and should not be used?
There was a problem hiding this comment.
Hmm, wait, I forgot to pass hex to Buffer.from('1345 4 '), that one would just throws TypeError: Invalid hex string, so there is nothing to compare :/
There was a problem hiding this comment.
Yeah, logically there is no way for it to be smaller. That would imply that you can encode more data by using an invalid string than a valid string.
It's not completely meaningless - e.g. if you allocate a Buffer with the size at least Buffer.byteLength, then the actual buffer will fit in it. Although I can't imagine a use case for it.
PR-URL: #11238 Refs: #11165 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: nodejs#11238 Refs: nodejs#11165 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: nodejs#11238 Refs: nodejs#11165 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: #11238 Refs: #11165 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: #11238 Refs: #11165 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: #11238 Refs: #11165 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: #11238 Refs: #11165 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
6 participants
Ref: #11165
Checklist
Affected core subsystem(s)
doc