Clarify Differences From Base64 Encoding - #102
Open
SyntaxNode wants to merge 1 commit into
Open
Conversation
SyntaxNode
commented
Jan 18, 2024
| <td>(pad)</td> | ||
| <td>=</td> | ||
| <td></td> | ||
| <td></td> |
Author
There was a problem hiding this comment.
GPP encoding does not use padding characters. Omitted from the table.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR provides extra clarity on the difference between GPP bit encoding and standard Base64 byte encoding, based on community feedback.
Fixed the encoding table to use base64-url instead of standard base64. We all use base64 right? That's with this repo is using.