Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The user-data field is kind of cursed and will accept plaintext or base64 encoded plaintext which it automatically detects somehow.
However sometimes this automatic detection does not occur and the user-data remains as undecoded base64 and I cannot find any specification of what the base64 format needs to look like for it to automatically decode it.
So, to avoid this issue I am just directly passing in the user-data without base64 encoding.
And come to think of it, its just simpler all around if we dont have to encode as base64.