Add the ability to provide arbitrary custom header claims #6
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.
As discussed in #4 this adds the ability to easily provide arbitrary additional header claims when calling
signJWT()
.The approach is the same as for the JWT body, allowing extra header claims of any type.
Additionally, the tests have been updated to show that extra header claims of can be provided without any linting errors and that they round-trip correctly.
Finally, fix the missing
await
in one of the tests which was tripping up in CI builds, but not locally.