Closed kokobd closed 8 months ago
Thanks for the PR. There are some major API-breaking changes I want to make at the same time as the switch to crypton. So I will deal with it later. Are you critically blocked by the lack of crypton support in jose at this time?
Are you critically blocked by the lack of crypton support in jose at this time?
No, I'm not in hurry. I'm in the process of removing cryptonite transitively in my project, and discovered this along the way. So using it in source-repository-package
is enough for my purpose.
It would be nice to support crypton before making breaking API changes.
That would enable the use of crypton without the immediate need to integrate the new API. (Note that the switch to crypton doesn't include any API change.)
At this point many projects on Hackage switched to crypton and additionally using cryptonite becomes a bit of a legacy.
It would be nice to support crypton before making breaking API changes.
That would enable the use of crypton without the immediate need to integrate the new API. (Note that the switch to crypton doesn't include any API change.)
At this point many projects on Hackage switched to crypton and additionally using cryptonite becomes a bit of a legacy.
I agree and I will support crypton in the current series, through a cabal flag.
Released https://hackage.haskell.org/package/jose-0.11. Thanks for your efforts and patience.
Resolves #114.
Bumped the major version as
cryptonite
was used in public API, at leastMonadRandom
inCrypto.JWT.signJWT