fix: the controller and basic procedure to use addSignatureRequest

Author: Victor Wiebe

src/entities/SecurityToken/Controller.ts

@@ -23,13 +23,9 @@ export class Controller extends SubModule {
    * Used by the issuer to permanently disable controller functionality
    * Signature is optional, and will be generated if it is not passed in
    */
-  public disableController = async (args: { signature?: string }) => {
-    const { signature } = args;
+  public disableController = async (args?: { signature?: string }) => {
     const { symbol } = this.securityToken;
-    const procedure = new DisableController(
-      signature ? { symbol, signature } : { symbol },
-      this.context
-    );
+    const procedure = new DisableController({ ...args, symbol }, this.context);
     return procedure.prepare();
   };
 

src/procedures/Procedure.ts

@@ -179,7 +179,7 @@ export abstract class Procedure<Args, ReturnType = void> {
       const transaction = {
         method: request,
         args,
-        postTransactionResolver,
+        postTransactionResolvers: [postTransactionResolver],
         tag: PolyTransactionTag.Signature,
       };
 

src/types/index.ts

@@ -228,8 +228,7 @@ export enum PolyTransactionTag {
   Signature = 'Signature',
 }
 
-export type MaybeResolver<T> = PostTransactionResolver<T> | T;
-
+export type MaybeResolver<T> = PostTransactionResolver<T, any> | T;
 export type MapMaybeResolver<T> = { [K in keyof T]: MaybeResolver<T[K]> };
 
 // TODO @monitz87: remake this interface when contract-wrappers exports the tx arguments