fix: \n character is handled different in windows

lukeautry · Oct 29, 2023 · bb53e2e · bb53e2e
1 parent 9a5ceb8
commit bb53e2e
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/packages/cli/src/metadataGeneration/typeResolver.ts b/packages/cli/src/metadataGeneration/typeResolver.ts
@@ -1103,13 +1103,13 @@ export class TypeResolver {
       .replace(/{|}/g, '_') // SuccessResponse_{indexesCreated-number}_ -> SuccessResponse__indexesCreated-number__
       .replace(/([a-z_0-9]+\??):([a-z]+)/gi, '$1-$2') // SuccessResponse_indexesCreated:number_ -> SuccessResponse_indexesCreated-number_
       .replace(/;/g, '--')
-      .replace(/\r\n/g, '\n')
       .replace(/([a-z})\]])\[([a-z]+)\]/gi, '$1-at-$2'); // Partial_SerializedDatasourceWithVersion[format]_ -> Partial_SerializedDatasourceWithVersion~format~_,
 
     //Safety fixes to replace all characters which are not accepted by swagger ui
-    const formattedName = preformattedName.replace(/[^A-Za-z0-9\-._]/g, match => {
+    let formattedName = preformattedName.replace(/[^A-Za-z0-9\-._]/g, match => {
       return `_${match.charCodeAt(0)}_`;
     });
+    formattedName = formattedName.replace(/92_r_92_n/g, '92_n'); //Windows uses \r\n, but linux uses \n.
 
     return formattedName;
   }