Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My previous attempt at adding a
DIDMethodResolver
protocol in #9 didn't really work out how I intended it to, so I reverted it.This PR re-introduces a
DIDMethodResolver
protocol, and handles the behaviors of a DID resolver much better.DIDMethodResolver
DIDMethodResolver
is a new protocol that defines what's required to resolve a DID method. There are two things:methodName
that's being resolvedfunc resolve(didURI: String) -> ResolutionResult
functionEach DID method implements this
DIDMethodResolver
with a struct. This struct can then initiated and registered withDIDResolver
, to customize the resolution experience for any SDK consumer's use case.DIDResolver
DIDResolver
now has a new function available on it:public static func register(resolver: DIDMethodResolver)
This is how an SDK consumer can customize the behavior of the resolution of any DID Method. For example, if a user wanted to customize the experience of resolving
did:ion
, they would do the following: