CreateInboxResponseMessage does not have @id and @type agent message properties set. This can cause issues for a generic agent message handler that uses @type for delegating message handling to a specific handler.
Changes proposed in this pull request:
Set random ID and correct type from RoutingTypeNames in CreateInboxResponseMessage constructor
Fixes: #
Would it also make sense to add a thread decorator referring back to the initial CreateInboxMessage? That would be more in line with Aries RFCs, but creating an inbox is generally using duplex communication, so it seems redundant.
Short description of what this resolves:
CreateInboxResponseMessagedoes not have@idand@typeagent message properties set. This can cause issues for a generic agent message handler that uses@typefor delegating message handling to a specific handler.Changes proposed in this pull request:
RoutingTypeNamesinCreateInboxResponseMessageconstructorFixes: #
Would it also make sense to add a thread decorator referring back to the initial
CreateInboxMessage? That would be more in line with Aries RFCs, but creating an inbox is generally using duplex communication, so it seems redundant.