fix(typescript-fetch): fix logic when stringEnums is explicitly set to false (#22466)

scarf005 · web-flow · commit 5a2503dc4913 · 2025-12-01T09:51:13.000+01:00
Passing `stringEnums=false` was incorrectly treated as `true`. This went unnoticed since the default behavior works as expected. Made the logic consistent with `typescript-axios`.
diff --git a/modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/TypeScriptFetchClientCodegen.java b/modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/TypeScriptFetchClientCodegen.java
@@ -283,6 +283,7 @@ public void processOpts() {
 
         if (additionalProperties.containsKey(STRING_ENUMS)) {
             this.setStringEnums(convertPropertyToBoolean(STRING_ENUMS));
+            additionalProperties.put("stringEnums", this.stringEnums);
         }
 
         if (additionalProperties.containsKey(FILE_NAMING)) {

Original file line number	Diff line number	Diff line change
`@@ -283,6 +283,7 @@ public void processOpts() {`
`283`	`283`
`284`	`284`	`if (additionalProperties.containsKey(STRING_ENUMS)) {`
`285`	`285`	`this.setStringEnums(convertPropertyToBoolean(STRING_ENUMS));`
	`286`	`+ additionalProperties.put("stringEnums", this.stringEnums);`
`286`	`287`	`}`
`287`	`288`
`288`	`289`	`if (additionalProperties.containsKey(FILE_NAMING)) {`