-
Notifications
You must be signed in to change notification settings - Fork 426
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
Ensure that decodeB64 returns a String rather than Bytes. #609
Conversation
The following is the coverage report on the affected files.
|
This changes the return value of the decodeB64 overload to ensure that it returns a string.
e76c8bc
to
76bf4a7
Compare
The following is the coverage report on the affected files.
|
/kind bug |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
I should probably have explained why it was originally When it's a string, it gets quoted when it's being inserted as an overlay value, what that means, is that previously, if you were decoding a base64 encoded JSON blob, the value that was inserted as, was a string, and not an object, so you couldn't use the fields. Essentially, if you had something like But, with the addition of parseJSON, this isn't so much of a problem, as you can decode the base64 and then parse the JSON.
|
Changes
This changes the return value of the decodeB64 overload to ensure that it returns a string.
Fixes #608
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Release Notes