fix: content type detection now considers matchers

pact-foundation · Mar 29, 2022 · 069da08 · 069da08
1 parent c77301a
commit 069da08
Showing 1 changed file with 7 additions and 13 deletions.
diff --git a/src/v3/pact.ts b/src/v3/pact.ts
@@ -22,14 +22,20 @@ export enum SpecificationVersion {
   SPECIFICATION_VERSION_V3 = 4,
 }
 
+const matcherValueOrString = (obj: unknown): string => {
+  if (typeof obj === 'string') return obj;
+
+  return JSON.stringify(obj);
+};
+
 const contentTypeFromHeaders = (
   headers: TemplateHeaders | undefined,
   defaultContentType: string
 ) => {
   let contentType: string | MatchersV3.Matcher<string> = defaultContentType;
   forEachObjIndexed((v, k) => {
     if (`${k}`.toLowerCase() === 'content-type') {
-      contentType = v;
+      contentType = matcherValueOrString(v);
     }
   }, headers || {});
 
@@ -70,18 +76,6 @@ export interface PactV3Options {
   logLevel?: 'trace' | 'debug' | 'info' | 'warn' | 'error';
 }
 
-// const logInvalidOperation = (op: string) => {
-//   throw new Error(
-//     `unable to call operation ${op}, this is probably a bug in Pact JS`
-//   );
-// };
-
-const matcherValueOrString = (obj: unknown): string => {
-  if (typeof obj === 'string') return obj;
-
-  return JSON.stringify(obj);
-};
-
 const readBinaryData = (file: string): Buffer => {
   try {
     const body = fs.readFileSync(file);