Skip to content

Conversation

@goncalo-frade-iohk
Copy link
Contributor

@goncalo-frade-iohk goncalo-frade-iohk commented Oct 4, 2025

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:

  • My PR follows the contribution guidelines of this project
  • My PR is free of third-party dependencies that don't comply with the Allowlist
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked the PR title to follow the conventional commit specification

@goncalo-frade-iohk goncalo-frade-iohk requested a review from a team as a code owner October 4, 2025 11:38
@goncalo-frade-iohk goncalo-frade-iohk force-pushed the feature/did-resolver-http branch 2 times, most recently from 87fae95 to 0b1e503 Compare October 4, 2025 12:34
Copy link
Contributor

@yshyn-iohk yshyn-iohk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@goncalo-frade-iohk goncalo-frade-iohk force-pushed the feature/did-resolver-http branch from 0b1e503 to 3efdb09 Compare October 27, 2025 18:27
This is quite extensive PR since it makes the DIDDocument codable.

Signed-off-by: goncalo-frade-iohk <goncalo.frade@iohk.io>
@goncalo-frade-iohk goncalo-frade-iohk force-pushed the feature/did-resolver-http branch from 3efdb09 to 3fec8b3 Compare October 27, 2025 18:31
Copy link

@FabioPinheiro FabioPinheiro left a 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)

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?

Copy link
Contributor Author

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.

@goncalo-frade-iohk goncalo-frade-iohk merged commit e0bd2ff into main Oct 30, 2025
4 checks passed
@goncalo-frade-iohk goncalo-frade-iohk deleted the feature/did-resolver-http branch October 30, 2025 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants