Skip to content
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

Merged
merged 21 commits into from
Jun 30, 2020
Merged

Integrate DIF Resolver #401

merged 21 commits into from
Jun 30, 2020

Conversation

Exulansis
Copy link
Collaborator

@Exulansis Exulansis commented Jun 8, 2020

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 the jolo-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 a IRegistry instance, but rather take a Registry class instead. This is a breaking API change.

VolkerSchiewe and others added 8 commits December 2, 2019 16:21
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
@mnzaki
Copy link
Contributor

mnzaki commented Jun 11, 2020

IMHO change this PR to the next branch and break the IRegistry interface

tests/integration/provision.ts Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
tests/integration/identity.integration.ts Outdated Show resolved Hide resolved
tests/integration/payment.integration.ts Show resolved Hide resolved
ts/identity/didDocument/types.ts Outdated Show resolved Hide resolved
ts/identityWallet/identityWallet.ts Outdated Show resolved Hide resolved
@Exulansis
Copy link
Collaborator Author

IMHO change this PR to the next branch and break the IRegistry interface

+1 The next branch is slightly out of date atm.

@Exulansis Exulansis changed the title 326/dif resolver Integrate DIF Resolver Jun 14, 2020
@Exulansis Exulansis self-assigned this Jun 14, 2020
@Exulansis Exulansis marked this pull request as ready for review June 19, 2020 14:30
@Exulansis Exulansis added finished new feature New feature or request and removed in progress labels Jun 19, 2020
@Exulansis Exulansis changed the base branch from develop to next June 19, 2020 14:46
@Exulansis
Copy link
Collaborator Author

I've changed the base to next.
It's out of date, and has a few PRs merged into it which develop does not contain.

We should decide what to do with next to proceed. I'd propose resetting it to match current developm or merge develop in, if the PRs there are useful.

@Exulansis
Copy link
Collaborator Author

Develop should be merged into next.

Copy link
Contributor

@chunningham chunningham left a 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.

ts/registries/jolocomRegistry.ts Show resolved Hide resolved
@chunningham chunningham merged commit 6310cc2 into next Jun 30, 2020
@chunningham chunningham deleted the 326/dif-resolver branch June 30, 2020 09:16
@chunningham chunningham restored the 326/dif-resolver branch June 30, 2020 09:21
@chunningham chunningham deleted the 326/dif-resolver branch June 30, 2020 09:22
@Exulansis Exulansis mentioned this pull request Jul 29, 2020
@Exulansis Exulansis mentioned this pull request Nov 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants