Add Ability to Decode JWT & Code Cleanup #6
+259
−238
Conversation
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
this was only used in creating sample json to pass to `dbo.JWT_Encode()`. However, that is on the user to determine how they create that json (use native json support instead)
sixfeetover
reviewed
Oct 29, 2021
sixfeetover
approved these changes
Oct 29, 2021
matthewdenaburgvc
approved these changes
Dec 10, 2025
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.
Background
In working with this, I separated out each of the functions into separate files for better readability and better tracking of individual file changes.
Following @johnjarrard's work on #2, I clean up the code formatting to match the standards in this project and used native
string_split.I also remove
dbo.XmlToJson(), as it is actually not needed in the core encoding/decoding functions.