fix: DidCommV2 - avoid breaking changes #1540
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to avoid breaking changes compared to the main branches.
AgentMessage
class which actually isDidCommV1Message
.AgentBaseMessage
is a common interface for V1/V2 - used internallyAttachment
for DidCommV1 message attachmentsSigningProvider
Differences with the
main
outOfBandInvitation
field of the OutOfBand record is optionalv2OutOfBandInvitation
TransportSession
-keys
andinboundMessage
refers to different types but it should not break implementations.TransportSession