-
Notifications
You must be signed in to change notification settings - Fork 83
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
did:peer:4
integration, bugfix, improvements
#1167
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1167 +/- ##
========================================
- Coverage 0.05% 0.05% -0.01%
========================================
Files 484 484
Lines 24184 24203 +19
Branches 4484 4490 +6
========================================
Hits 13 13
- Misses 24171 24190 +19
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Patrik Stas <patrik.stas@absa.africa>
Signed-off-by: Patrik Stas <patrik.stas@absa.africa>
Signed-off-by: Patrik Stas <patrik.stas@absa.africa>
Signed-off-by: Patrik Stas <patrik.stas@absa.africa>
Patrik-Stas
force-pushed
the
didechange/didpeer4
branch
from
March 25, 2024 11:43
018171a
to
4bfbdec
Compare
Patrik-Stas
changed the title
Didechange/didpeer4
Mar 25, 2024
did:peer:4
integration, bugfix, improvements
Signed-off-by: Patrik Stas <patrik.stas@absa.africa>
Patrik-Stas
force-pushed
the
didechange/didpeer4
branch
from
April 1, 2024 11:26
171b732
to
20c48fa
Compare
GHkrishna
pushed a commit
to GHkrishna/aries-vcx
that referenced
this pull request
Apr 16, 2024
* did:peer:4 integration, bugfix, improvements (hyperledger#1167) Signed-off-by: Patrik Stas <patrik.stas@absa.africa>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
did:peer:4
in didexchange (producedid:peer:4
in outgoing messages for both requester and responder)did:peer:2
(well, or any other DID method we support)Additional updates:
DidDocument
:assertion_method_by_key(&self, id: &str)
verification_method_by_id(&self, id: &str)
key_agreement_by_id(&self, id: &str)
capability_invocation_by_id(&self, id: &str)
capability_delegation_by_id(&self, id: &str)
DidDocument
, generally following pattern:add_authentication(&mut self, method: VerificationMethodKind)
add_authentication_object(&mut self, method: VerificationMethod)
add_authentication_ref(&mut self, reference: DidUrl)
Fixes
contextualize_to_did_doc
which causesdid:peer:4
to not fully decodeError handling changes
PeerDid<Numalgo4>::short_form(&self)
does not returnResult
, but instead usesexpect()
which should never happens (see safety note in the code).DidPeer4ConstructionDidDocument::contextualize_to_did_doc(&self, did_peer_4: &PeerDid<Numalgo4>)
is now also usingpanic
upon conversion of DID type to URI type. Every DID is URI and therefore this should never panic. If panic occurs, it strictly indicates either: