-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor jws
to be aligned with specification concepts
#143
Comments
why not keep it and yes! I like this proposed way very much, very similar to web5-go right? not sure why we need this function:
We can just construct the Header internally? |
yup I'm cool with sticking with yup, very similar to web5-go yeah I think I'm on board with not moving forward with the |
The v2 is looking great. #162 Just for transparency, we had an upgrade path planned out to make v2 of jws, jwk, and vc, and once its all in place working nice together can rename and gut out the old one. So basically if all this looks good we can merge in 162 |
* Refactor jws #143 * update * lint --------- Co-authored-by: Kendall Weihe <[email protected]>
* Refactor jws TBD54566975#143 * update * lint --------- Co-authored-by: Kendall Weihe <[email protected]>
I take issue with a number of things inside the
jws
cratenew_from_encoded()
andencode()
both only used internally (albeitencode()
is used invc.rs
but that needs to be changed (TODO working on another ticket for refactoring thejwt
crate) -- both of these could be removedsplice_parts
is out on it's own, and technically is splicing a compact JSJwsError
but it's the only error in the crate, so why not just call itError
?I would propose we rethink this crate altogether with the following design:
(I'm going to also include the "decode" design from this ticket #118)
These changes would break at least
jwt
andcredentials
so if we choose to move forward with this proposal then we should probably string these work items togetherThe text was updated successfully, but these errors were encountered: