Fix integer type representation in OpenAPI schema generation

This commit fixes an issue where query parameters with integer types were incorrectly being represented as 'number' type in the generated OpenAPI specifications. Now
integer types are properly represented as 'integer' in the schema, ensuring that tools consuming the OpenAPI specification correctly understand the expected data type
of query parameters.

Author: youngjungithub

packages/openapi-generator/src/openapi.ts

@@ -20,18 +20,23 @@ export function schemaToOpenAPI(
     switch (schema.type) {
       case 'boolean':
       case 'string':
-      case 'number':
         return {
           type: schema.type,
           ...(schema.enum ? { enum: schema.enum } : {}),
           ...defaultOpenAPIObject,
         };
-      case 'integer':
+      case 'number':
         return {
           type: 'number',
           ...(schema.enum ? { enum: schema.enum } : {}),
           ...defaultOpenAPIObject,
         };
+      case 'integer':
+        return {
+          type: 'integer',
+          ...(schema.enum ? { enum: schema.enum } : {}),
+          ...defaultOpenAPIObject,
+        };
       case 'null':
         // TODO: OpenAPI v3 does not have an explicit null type, is there a better way to represent this?
         // Or should we just conflate explicit null and undefined properties?