the use of Resolver type from did-resolver is too restrictive

[mirceanis]

The Resolver class from did-resolver is declared with the private fields included, which makes it hard to implement matching type signatures.

For example, the following object cannot be used directly in verifyJWT or similar methods that require Resolver.

const resolver = {
  resolve: (didURL: string, options: DIDResolutionOptions) => Promise.resolve(<DIDResolutionResult>{/*...*/})
}

The error is :

Type '{ resolve: (didUrl: string, options: DIDResolutionOptions) => Promise<DIDResolutionResult>; }' is missing the following properties from type 'Resolver': registry, cache

or

Type 'import("node_modules/did-resolver/lib/resolver").Resolver' is not assignable to type 'import("node_modules/did-jwt/node_modules/did-resolver/lib/resolver").Resolver'.
      Types have separate declarations of a private property 'registry'.

There is a workaround to use something like (resolver as unknown) as Resolver but this is not intuitive and annoying.

Only the required signature of the Resolver type should be required by this lib; without the private members.

[uport-automation-bot]

🎉 This issue has been resolved in version 5.1.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀