question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add support for didResolutionMetadata and didDocumentMetadata

See original GitHub issue

According to did-core a resolver function should have the following abstract form:

resolve(did, resolutionOptions) →
   « didResolutionMetadata, didDocument, didDocumentMetadata »

Currently the function signature for this library looks like this:

resolve(did: string): Promise<DIDDocument>

We should introduce a breaking change that adds support for returning didResolutionMetadata and didDocumentMetadata. It should be possible to implement this in a way in which all resolvers won’t break with the new version of this package, but won’t provide additional metadata until they implement the new interface.

The new function signature would look something like this:

interface ResolutionResult {
  didDocument: DIDDocument
  didResolutionMetadata: DIDResolutionMetadata
  didDocumentMetadata: DIDDocumentMetadata
}

resolve(did: string, resolutionOptions: ResolutionOptions): Promise<ResolutionResult>

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

4reactions
oedcommented, Feb 25, 2021

I’m planning to do that yes! 😃

0reactions
uport-automation-botcommented, Mar 2, 2021

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Read more comments on GitHub >

github_iconTop Results From Across the Web

Decentralized Identifier Resolution (DID Resolution) v0.3
( didResolutionMetadata, didDocument, didDocumentMetadata ) ... Append the DID fragment to the output service endpoint URL .
Read more >
Decentralized Identifiers (DIDs) v1.0 - W3C
Indeed, almost all types of identifier systems can add support for DIDs. ... This specification defines the following DID resolution metadata properties:.
Read more >
didkit-cli - crates.io: Rust Package Registry
Command-line interface for Verifiable Credentials and Decentralized Identifiers.
Read more >
did-jwt - npm
If your DID method requires a different signing algorithm than what is already supported, please create an issue. Installation. npm install did- ...
Read more >
did-jwt | Yarn - Package Manager
The did-JWT library allows you to sign and verify JSON Web Tokens (JWT) using ES256K and EdDSA algorithms. The non-standard ES256K-R is also...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found