-
Notifications
You must be signed in to change notification settings - Fork 14
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: merging multiple PeerDID classes #130
Conversation
This I don't agree. Why should the peer DID be in the domain? |
Lets try to also be careful and asses if this is introducing a breaking change, etc + also make sure the demo content run as expected + tests. |
53c1ed5
to
3d28da7
Compare
@goncalo-frade-iohk moved the code to peerdid i think its also the right move, it was there previous thats ok but now in peerDID, waiting for plugins to happen. |
6a5869a
to
d95de6b
Compare
d95de6b
to
43796c4
Compare
BREAKING CHANGE: If you have imported Domain.PeerDID in your typescript application, you will need to re-import from PeerDID directly
43796c4
to
521ad4c
Compare
Co-authored-by: Francisco Javier Ribó Labrador <[email protected]> BREAKING CHANGE: If you have imported Domain.PeerDID in your typescript application, you will need to re-import from PeerDID directly Signed-off-by: Francisco Javier Ribó Labrador <[email protected]>
Description
Merge two PeerDID classes into Domain model.
Jira link
https://input-output.atlassian.net/browse/ATL-6215
Checklist