From 4c075766cf19ba0d2a978fad1fcaa43719968da1 Mon Sep 17 00:00:00 2001
From: Claus-Peter Huebner <claus-peter.huebner@email.de>
Date: Thu, 20 Jul 2023 23:18:45 +0200
Subject: [PATCH] 2nd dlt-trigger in TransactionLinkResolver, but as
 TODO-comment

---
 .../src/graphql/resolver/TransactionLinkResolver.ts | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/backend/src/graphql/resolver/TransactionLinkResolver.ts b/backend/src/graphql/resolver/TransactionLinkResolver.ts
index 282e6662a..b3fe846f4 100644
--- a/backend/src/graphql/resolver/TransactionLinkResolver.ts
+++ b/backend/src/graphql/resolver/TransactionLinkResolver.ts
@@ -290,6 +290,19 @@ export class TransactionLinkResolver {
           await queryRunner.manager.update(DbContribution, { id: contribution.id }, contribution)
 
           await queryRunner.commitTransaction()
+
+          /* TODO not the right place, because its inside semaphore locks
+          // send transaction via dlt-connector
+          // notice: must be called after transaction are saved to db to contain also the id
+          // we use catch instead of await to prevent slow down of backend
+          // because iota pow calculation which can be use up several seconds
+          const dltConnector = DltConnectorClient.getInstance()
+          if (dltConnector) {
+            dltConnector.transmitTransaction(transaction).catch(() => {
+              logger.error('error on transmit creation transaction')
+            })
+          }
+*/
           await EVENT_CONTRIBUTION_LINK_REDEEM(
             user,
             transaction,