Now with v5 landed, we reduced quite some technical debt in the department of the verifier, but let's not stop there. This will serve as a meta-issue detailing the current plans for developing this library. Please note, that development might take a slower pace than others, considering the large number of people depending on this library.
We probably should decide at which point we want to "open" main to v6 changes - possibly still allowing patches to an old v5 branch. Alternatively we could stay on v5 for main for a while and have an experimental v6 branch that is the target of all pull requests that are potentially containing breaking changes.
v6
So for v6, I want to focus on enhancing the developer experience as well as fixing remaining bugs we forgot in v5 that are potentially API breaking.
Bug fixes
Quality of life
Now with
v5landed, we reduced quite some technical debt in the department of the verifier, but let's not stop there. This will serve as a meta-issue detailing the current plans for developing this library. Please note, that development might take a slower pace than others, considering the large number of people depending on this library.We probably should decide at which point we want to "open" main to
v6changes - possibly still allowing patches to an oldv5branch. Alternatively we could stay onv5for main for a while and have an experimentalv6branch that is the target of all pull requests that are potentially containing breaking changes.v6So for
v6, I want to focus on enhancing the developer experience as well as fixing remaining bugs we forgot inv5that are potentially API breaking.Bug fixes
GetIDin theClaimsinterface ? #334Quality of life
KeyfuncandSignedString#337