Expose and document existing 'json' option in jws.decode and jws.createVerify APIs #105
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.
Description
The
jsonoption is currently accepted by thejws.decodeAPI, although it is not documented in repo. From its usage, it seems it intends to enable configuring how the payload should be parsed when thetypis not set to 'JWT' on the JWS header.This change:
a) documents the option as part of the API
b) adds support for the option via the
jws.createVerifyAPI, which will pass through the option tojws.decodeinternally.Testing
Added tests for when:
the
typis set to 'JWT'the
typis missingthe
typis invalidthe
typis invalid, butjsonoption is set to true, forcing parsing of payload as JSONhandle null value for
jsonoption as expectedThis change adds test coverage for new/changed/fixed functionality
Checklist