Change urlSafe to be RFC4648 compliant #29
Merged
Conversation
This file contains 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
This encodes now + to - and / to _ as stated in the RFC. Sadly now one more replace() call had to be added which will impact the performance of the urlSafe benchmarks.
|
Just as a side note. Newer versions of node.js (14.8+) support base64url as an encoding option so eventually you should be able to use that here! Once 12.x drops off long term support in April, all supported versions of node.js will have it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 encodes now + to - and / to _ as stated in the RFC.
Sadly now one more replace() call had to be added which
will impact the performance of the urlSafe benchmarks.
Closes #28