fix: expose functionality to create peerDIDs outside of the agent.

[elribonazo]

I would like to propose to expose the peerdid create function and make it available as part of the bundle in order to be able to create peerdids from existing keys outside of the agent.

The new exportes classes had been documented in the past so they are okey.

Description

No PR, this is an open proposal of improvement.

Jira link

N/A

Checklist

• Self-reviewed the diff
• New code has inline documentation
• New code has proper comments/tests
• Any changes not covered by tests have been tested manually

[github-actions]

Lines	Statements	Branches	Functions
	36.86% (1610/4367)	25.73% (712/2767)	40.14% (505/1258)

JUnit

Tests	Skipped	Failures	Errors	Time
298	2 💤	0 ❌	0 🔥	1m 2s ⏱️

[curtis-h]

nothing against this in theory, but I think we've got some consideration to do for PeerDIDs
I noticed on Friday we've got two classes (fix here #130)
but I'm also wondering why is "peer-did" it's own folder? doesn't this belong in Castor?

[goncalo-frade-iohk]

I got the same doubt as @curtis-h shouldn't this be inside of castor?

[goncalo-frade-iohk]

If there is a requirement to make our funcionality of creating peer did public, lets do it inside castor. And make that class public by importing Castor.

[elribonazo]

If there is a requirement to make our funcionality of creating peer did public, lets do it inside castor. And make that class public by importing Castor.

My mistake @goncalo-frade-iohk Castor satisfies that indeed, thank you!
Closing