-
Notifications
You must be signed in to change notification settings - Fork 511
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
fix: resolve dids following new endpoint rules #1863
fix: resolve dids following new endpoint rules #1863
Conversation
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Codecov Report
@@ Coverage Diff @@
## main #1863 +/- ##
==========================================
+ Coverage 93.79% 93.80% +0.01%
==========================================
Files 539 539
Lines 34081 34101 +20
==========================================
+ Hits 31967 31990 +23
+ Misses 2114 2111 -3 |
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
service_endpoint=endpoint_url, | ||
recipient_keys=[recipient_key.id], | ||
routing_keys=routing_keys, | ||
accept=["didcomm/v2"], |
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.
Isn't it an issue that it resolves to accept only didcomm/v2, while we don't actually support that yet? Or does it not matter because this endpoint isn't examined anyway.
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.
Yeah, I think in this case, we're just constructing the DID Document as the DID Method spec outlines and whether we use the all of the services outlined in the doc is another question. We will be essentially ignoring them for now since we're only looking for the did-communication
type.
Naive solution to the issue raised by @TimoGlastra in #1313.