aries-framework-javascript GitHub

feat(basic-messages): improve sending error handling

Currently, when an outbound message is sent as a result of calling a module/API method and a transport error happens, an exception is thrown without any retry mechanism (unless handled externally by the outbound transporter object). In the particular case of Basic Messages, when such situation happens, a record is created but there are no means from the calling application to know its id and delete it or mark it as failed in the UI. This PR addresses this issue by throwing in `BasicMessageModule.sendMessage` a new kind of error: `MessageSendingError`, which includes the message itself and the associated record. The reason of adding the message is to open the possibility for the calling application to retry sending if it wants (not something so straightforward though, but feasible). The same strategy could potentially be extended to methods from other modules that also create records and send messages in a single step (e.g. sendQuestion, proposeCredential, offerCredential). Signed-off-by: Ariel Gentile <gentilester@gmail.com>

Created At 2022-10-06 00:05:18 +0000 UTC

PR #1044	feat: exposed findByQuery method in module services and added some of the necessary tests for the switch
	…ecessary tests for the switch Signed-off-by: Jim Ezesinachi <ezesinachijim@gmail.com>

Created At 2022-10-05 13:26:00 +0000 UTC

PR #1043

feat: possibility to set masterSecretId inside of WalletConfig

</td> </tr> </table>

Created At 2022-10-04 15:48:19 +0000 UTC

</div>

PR #1040

feat(question-answer): separate logic to a new module

Separated the question-answer logic to a new module. Since it is now a separate module, if core gets released before the question-answer module it will not be included in the core anymore. This is a breaking change and might cause some headaches. We can just merge it in after 0.3.0 is released and take our time with a strategy to add it back into the core for now. --- I could also keep the question-answer module inside the core and release this one separately. When we do a new 0.3.1 or 0.4.0 release the can remove it and make it dependent on this one.

Created At 2022-10-02 15:45:39 +0000 UTC