-
Notifications
You must be signed in to change notification settings - Fork 7
feat(castor)!: http did resolver #221
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
Conversation
87fae95 to
0b1e503
Compare
EdgeAgentSDK/Castor/Sources/Resolvers/GitHubPrismDIDResolver.swift
Outdated
Show resolved
Hide resolved
yshyn-iohk
left a comment
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.
🚀
0b1e503 to
3efdb09
Compare
This is quite extensive PR since it makes the DIDDocument codable. Signed-off-by: goncalo-frade-iohk <goncalo.frade@iohk.io>
3efdb09 to
3fec8b3
Compare
FabioPinheiro
left a comment
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.
For my little understanding looks good
|
|
||
| public func resolve(did: Domain.DID) async throws -> Domain.DIDDocument { | ||
| do { | ||
| return try await shortFormResolver.resolve(did: did) |
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.
Does this try to resolve the short form. Independently if the given DID is a long or a short form, right?
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.
Yes this is dependent on the dependency injection, but our short form resolver is here EdgeAgentSDK/Castor/Sources/Resolvers/EndpointShortFormPrismDIDRemoteResolver.swift, and is as you say it will work for short and long form independently.
Description:
This is quite extensive PR since it makes the DIDDocument codable.
Alternatives Considered (optional):
Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.
Checklist: