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
enhancement(remap): Add charset parameter to encode_base64 function #6065
Conversation
Signed-off-by: Luc Perkins <luc@timber.io>
Signed-off-by: Luc Perkins <luc@timber.io>
Signed-off-by: Luc Perkins <luc@timber.io>
Signed-off-by: Luc Perkins <luc@timber.io>
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.
Looks good!
I think, with this addition, the function should be marked as always fallible given that users can pass invalid charsets.
Signed-off-by: Luc Perkins <luc@timber.io>
@jszwedko Ah yes, you're quite right about the fallibility of the charset. I've updated that. |
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.
🥳
@jszwedko Though, quick nit slash FYI: it doesn't make the function always fallible. Rather, it makes the function fallible if |
Signed-off-by: Luc Perkins <luc@timber.io>
95be921
to
03e8d93
Compare
Adds a
charset
parameter to theencode_base64
function with two possible values:standard
andurl_safe
. It's fairly trivial to add others in the future.Closes #6011