Generation via swagger ui gives an incorrect default value for limit numbers

Q&A (please complete the following information)

• OS: RHEL 7 (docker)
• Browser: yandex broser
• Version: latest container (swagger ui)
• Method of installation: docker
• Swagger/OpenAPI version: 3.0.2

Content & configuration

Example Swagger/OpenAPI definition:

Path is:
      responses:
        "200":
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/checkNegativeNumbers"

ComponentSchema is:
    checkNegativeNumbers:
      type: "object"
      properties:
        negativeInteger:
          type: "integer"
          maximum: -1
      required:
      - "nonPositiveInteger"
      - "negativeInteger"

Describe the bug you're encountering

When specifying a negative maximum value (such as -1), swagger displays correctly. But if we generate a spring server, we get an incorrect default value of zero.

To reproduce...

Use swagger ui.

Steps to reproduce the behavior:

1. Define any type with a number.
2. Set maximum = -1.
3. Generate a spring server.

Expected behavior

Json with a valid number in the generated code. (it very useful for autotesting)

Screenshots

Start in Swagger UI with the supplied OpenAPI 3.0.2 definition and reproduce Spring server generation for an integer with maximum -1. Trace how the negative maximum is used for the generated default value; done means the generated code contains a valid negative number instead of zero.