-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate DIF Resolver #401
Conversation
…esolver package of DIF
The mocks / stubs needed an update. The goal was to have the tests pass after the merge.
… test one No API for injecting a custom resolver seems to be present. Will have to be addressed later.
Tests currently fail because of a breaking change in #399. Furthermore, a better API for passing in a custom resolover is needed
IMHO change this PR to the |
instanceOf assertions can be used again.
…pposed to IRegistry
…ests The change was pushed accidently.
+1 The next branch is slightly out of date atm. |
I've changed the base to We should decide what to do with |
Develop should be merged into |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that we're merging into next, we could make a few more breaking changes to avoid some boilerplate related to how we used to use the registry. This is not a blocking suggestion though.
Partially addresses #326
Integrates the DID-Resolver module into our library. Reduces the usage of the
IRegistry
interface, offloading some of the responsibility /complexity to thejolo-did-method
module.The API on functions making use of a resolver (e.g.
utils/validation
,identityWallet.validateJWT
) has been updated to no longer take aIRegistry
instance, but rather take aRegistry
class instead. This is a breaking API change.