-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
buffer.transcode: document valid encodings #15632
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
Comments
There is a section in that document specifically about character encodings. |
At least one character encoding specified there ( |
If you like I could rename this ticket "buffer.transcode should support base64" which would remove the confusion. |
Fixes: #15632 PR-URL: #22263 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Fixes: nodejs/node#15632 PR-URL: nodejs/node#22263 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
The documentation for
buffer.transcode
states:However, the documentation does not specify which encodings are valid.
(I was trying to transcode a Buffer into a Buffer with the same bytes, base64 encoded. My goal was to replace the
+
and/
characters with-
and_
without needing to create an entirely new string or call.replace
).The text was updated successfully, but these errors were encountered: