Simplify fix: avoid tagging JavaScript enums as 'type'

Co-authored-by: mrlubos <[email protected]>

Author: Copilot

packages/codegen-core/src/bindings/utils.ts

@@ -55,8 +55,6 @@ export const createBinding = ({
     if (symbol.meta?.kind === 'type') {
       typeNames.push(name);
     }
-    // For 'value-and-type' kind (JavaScript enums), we don't add to typeNames
-    // so they won't be exported as type-only
   }
   // cast type names to names to allow for cleaner API,
   // otherwise users would have to define the same values twice

packages/openapi-ts/src/plugins/@hey-api/typescript/export.ts

@@ -130,9 +130,6 @@ export const exportType = ({
           objectType: typeofType,
         }),
       });
-
-      // Mark this symbol as containing both value and type
-      symbol.meta = { ...symbol.meta, kind: 'value-and-type' };
       plugin.setSymbolValue(symbol, [objectNode, node]);
       return;
     } else if (

packages/openapi-ts/src/plugins/@hey-api/typescript/plugin.ts

@@ -497,10 +497,17 @@ const handleComponent = ({
   schema: IR.SchemaObject;
 }) => {
   const type = schemaToType({ plugin, schema });
+
+  // Don't tag JavaScript enums as 'type' since they export both values and types
+  const isJavaScriptEnum =
+    schema.type === 'enum' &&
+    plugin.config.enums.enabled &&
+    plugin.config.enums.mode === 'javascript';
+
   const symbol = plugin.registerSymbol({
     exported: true,
     meta: {
-      kind: 'type',
+      kind: isJavaScriptEnum ? undefined : 'type',
     },
     name: buildName({
       config: plugin.config.definitions,