feat: removed undefined from sage response headers

#6
eddienubes · Feb 12, 2024 · 8eaf7d3 · 8eaf7d3
1 parent 87f140e
commit 8eaf7d3
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 3 deletions.
diff --git a/src/Sage.ts b/src/Sage.ts
@@ -17,7 +17,7 @@ import {
   wrapArray,
   parseSetCookieHeader
 } from './utils.js';
-import { SageHttpResponse } from './SageHttpResponse.js';
+import { SageHttpResponse, SageResponseHeaders } from './SageHttpResponse.js';
 import path from 'node:path';
 import { FormDataOptions } from './FormDataOptions.js';
 import { createReadStream } from 'node:fs';
@@ -279,7 +279,7 @@ export class Sage {
         statusCode: res.statusCode,
         status: res.statusCode,
         statusText: statusCodeToMessage(res.statusCode),
-        headers: res.headers,
+        headers: res.headers as SageResponseHeaders,
         body: json,
         text: text,
         ok: isOkay(res.statusCode),

diff --git a/src/SageHttpResponse.ts b/src/SageHttpResponse.ts
@@ -19,7 +19,7 @@ export interface SageHttpResponse {
    * The mapping of status codes to status messages as defined in the HTTP/1.1 specification
    */
   statusText: HttpStatusText;
-  headers: Record<string, string | string[] | undefined>;
+  headers: SageResponseHeaders;
 
   /**
    * True if the status code falls in the range 200-299
@@ -46,3 +46,5 @@ export interface SageHttpResponse {
    */
   cookies: Record<string, CookieOptions>;
 }
+
+export type SageResponseHeaders = Record<string, string | string[]>;