Merge pull request #21 from AEB-labs/custom-input-operation-args

feature: implement custom operation input args hook

src/soap2graphql/schema-resolver.ts

@@ -222,18 +222,19 @@ export class SchemaResolver {
     }
 
     createSoapOperationFieldArgs(operation: SoapOperation): GraphQLFieldConfigArgumentMap {
-        const args: GraphQLFieldConfigArgumentMap = {};
+        let args: GraphQLFieldConfigArgumentMap = {};
         const inputType = operation.inputType();
         switch (inputType.kind) {
             case 'complexType':
                 const gqlInputType = this.inputResolver.resolve({
                     type: operation.inputType(),
                 }) as GraphQLInputObjectType;
-                return gqlInputType.getFields();
+                args = gqlInputType.getFields();
+                break;
             case 'simpleType':
                 args['input'] = { type: this.scalarResolver.resolve(inputType) };
         }
-        return args;
+        return { ...args, ...(this.options.additionalOperationArgs || {}) };
     }
 
     resolveSoapOperationReturnType(operation: SoapOperation): GraphQLOutputType {

src/soap2graphql/soap2graphql.ts

@@ -5,6 +5,7 @@ import { SoapCaller } from './soap-caller';
 import { GraphQLSchemaConfig } from 'graphql/type/schema';
 import { SchemaResolver } from './schema-resolver';
 import { Logger } from './logger';
+import { GraphQLFieldConfigArgumentMap } from 'graphql/index';
 
 /**
  * Options for the GraphQL schema.
@@ -84,6 +85,12 @@ export type SchemaOptions = {
      * default: __attributes
      */
     attributesKey?: string;
+
+    /**
+     * Possibility to add custom input fields to each operation mutation e. g. for metadata or http headers.
+     * You'll probably want to implement a custom NodeSoapCaller when using this field.
+     */
+    additionalOperationArgs?: GraphQLFieldConfigArgumentMap;
 };
 
 export function createSchemaConfig(