MinLength and maxLength are missing in Zod generated schema

[shatynska]

What version of kubb is running?

2.12.5

What platform is your computer?

Windows, use WSL

What version of external packages are you using(@tanstack-query, MSW, React, Vue, ...)

"zod": "^3.22.4"

What steps can reproduce the bug?

My OpenApi 3.1

...
"LoginDto": {
        "type": [
          "object"
        ],
        "properties": {
          "identifier": {
            "type": [
              "string"
            ],
            "minLength": 3,
            "maxLength": 40
          },
          "password": {
            "type": [
              "string"
            ],
            "minLength": 8,
            "maxLength": 20
          }
        },
        "required": [
          "identifier",
          "password"
        ]
      },
...

My Kubb config:

...
    createSwaggerZod({
      output: {
        path: './zod',
      },
      group: { type: 'tag' },
    }),
...

I recieved:

export const loginDtoSchema = z.object({
  identifier: z.string(),
  password: z.string(),
});

How often does this bug happen?

Every time

What is the expected behavior?

export const loginDtoSchema = 
  z.object({
    identifier: z.string().min(3).max(40),
    password: z.string().min(8).max(20),
  });

Swagger/OpenAPI file?

{
  "openapi": "3.1.0",
  "paths": {
    "/api/auth/login": {
      "post": {
        "operationId": "AuthController_login",
        "summary": "Login user",
        "parameters": [],
        "requestBody": {
          "required": true,
          "content": {
            "application/json": {
              "schema": {
                "$ref": "#/components/schemas/LoginDto"
              }
            }
          }
        },
        "responses": {
          "201": {
            "description": "",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/LoginResponseDto"
                }
              }
            }
          }
        },
        "tags": [
          "auth"
        ]
      }
    },
  },
  "info": {
    "title": "",
    "description": "",
    "version": "0.0.1",
    "contact": {
    }
  },
  "tags": [
    {
      "name": "profiles",
      "description": ""
    }
  ],
  "servers": [],
  "components": {
    "securitySchemes": {
      "bearer": {
        "scheme": "bearer",
        "bearerFormat": "JWT",
        "type": "http"
      }
    },
    "schemas": {
      "LoginDto": {
        "type": [
          "object"
        ],
        "properties": {
          "identifier": {
            "type": [
              "string"
            ],
            "minLength": 3,
            "maxLength": 40
          },
          "password": {
            "type": [
              "string"
            ],
            "minLength": 8,
            "maxLength": 20
          }
        },
        "required": [
          "identifier",
          "password"
        ]
      },
      "LoginResponseDto": {
        "type": [
          "object"
        ],
        "properties": {
          "accessToken": {
            "type": [
              "string"
            ]
          }
        },
        "required": [
          "accessToken"
        ]
      }
    }
  }
}

Additional information

I notice that such bug have already appeared and was fixed: #770 (comment) , but I got it.
And similar one was with an array: #806 (comment)

[stijnvanhulle]

@shatynska We still have some issues with OpenAPI 3.1.0, same for this one. I will have a look later this week to resolve this :)