feat: allow fct and prf to be nullable. Fixes #98 #99
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
Allows
fctandprfto be nullable when consuming, and adhering to canonicalization, will not encode empty values in the resulting JWT.Link to issue
#98
Type of change
This makes rs-ucan adhere to the spec as of 0.9.0 w/r/t
prfandfctfields which MAY be undefined. This is a breaking change w/r/t some interfaces, but notably also the canonicalization.Test plan (required)
Updated existing tests