-
Notifications
You must be signed in to change notification settings - Fork 53
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
Readme errata #49
Labels
Comments
It's a bug, but not only in the readme, also in the ethr-did-resolver. See also #52 |
mirceanis
added a commit
that referenced
this issue
Apr 14, 2021
BREAKING CHANGE: new did core spec uses different format for DID documents and resolution. BREAKING CHANGE: Now using ethers.js which means that providers and signers may have a different API BREAKING CHANGE: default export was removed closes #50 closes #59 closes #21 closes #49 closes #51 closes #52
mirceanis
added a commit
that referenced
this issue
Apr 14, 2021
BREAKING CHANGE: new did core spec uses different format for DID documents and resolution. BREAKING CHANGE: Now using ethers.js which means that providers and signers may have a different API BREAKING CHANGE: default export was removed closes #50 closes #59 closes #21 closes #49 closes #51 closes #52 closes #57 closes #58
mirceanis
added a commit
that referenced
this issue
Apr 15, 2021
* chore(deps): update deps * feat: adapt to latest did core spec BREAKING CHANGE: new did core spec uses different format for DID documents and resolution. BREAKING CHANGE: Now using ethers.js which means that providers and signers may have a different API BREAKING CHANGE: default export was removed closes #50 closes #59 closes #21 closes #49 closes #51 closes #52 closes #57 closes #58
uport-automation-bot
pushed a commit
that referenced
this issue
Apr 15, 2021
# [2.0.0](1.3.0...2.0.0) (2021-04-15) ### Features * adapt to latest did core spec and libs ([#61](#61)) ([839079d](839079d)), closes [#50](#50) [#59](#59) [#21](#21) [#49](#49) [#51](#51) [#52](#52) [#57](#57) [#58](#58) ### BREAKING CHANGES * new did core spec uses different format for DID documents and resolution. * Now using ethers.js which means that providers and signers may have a different API * default export was removed
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Hi team,
The readme states 'An example of a DID document resolved using the Ethr-Did-Resolver:'
The DID v1.0 states in the specs registry:
Ref: https://w3c.github.io/did-spec-registries/#ethereumaddress
Is the readme outdated? I'm not sure if this is an error
The text was updated successfully, but these errors were encountered: