chore(gateways): modify responses from the contract to match our curr…

…ent strucutre

This behavior could easily be moved to the contract, there is not a specific reason why `result` has to be the response of any read interactions

src/router.ts

@@ -76,22 +76,38 @@ router.get(
   // calls the read interaction handler with the function name set to gateways
   `/v1/contract/:contractTxId${ARWEAVE_TX_ID_REGEX}/gateways`,
   blocklistMiddleware,
-  (ctx: KoaContext) => {
+  async (ctx: KoaContext) => {
     ctx.params.functionName = 'gateways';
-    return contractReadInteractionHandler(ctx);
+    await contractReadInteractionHandler(ctx);
+
+    // map the response to the expected format
+    const { result, ...restOfBody } = ctx.body as any;
+    ctx.body = {
+      ...restOfBody,
+      gateways: result,
+    };
   },
 );
 router.get(
   // calls the read interaction handler with the function name set to gateway and target set to the path param
   `/v1/contract/:contractTxId${ARWEAVE_TX_ID_REGEX}/gateways/:address${ARWEAVE_TX_ID_REGEX}`,
   blocklistMiddleware,
-  (ctx: KoaContext) => {
+  async (ctx: KoaContext) => {
     ctx.params.functionName = 'gateway';
     ctx.query = {
       ...ctx.query,
       target: ctx.params.address,
     };
-    return contractReadInteractionHandler(ctx);
+    await contractReadInteractionHandler(ctx);
+
+    // map the response to the expected format
+    const { result, ...restOfBody } = ctx.body as any;
+    ctx.body = {
+      ...restOfBody,
+      gateway: {
+        [ctx.params.address]: result,
+      },
+    };
   },
 );
 router.get(