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.
Initial work on extracting DIDComm out of core. For the moment, all features are still present on core package, but moved into an internal "didcomm" module that eventually will be extracted along other DIDcomm dependent modules, such as proofs and credentials.
All DIDComm-related fields in AgentConfig were moved to DidCommModuleConfig. As such, some DIDComm-related Agent API methods such as the ones for transport and feature registration are now part of DIDComm module API (for example,
agent.didcomm.features
oragent.didcomm.registerOutboundTransport
).Lots of TODO:
pack
andunpack
methods and make them part of another kind of service (which can be also owned by the module that implements the wallet, like AskarModule)module.register()
and we need to ensure that DIDComm module and its objects have been registered