exclusiveMin shows [0...0]

[takumi-ricoh]

Describe the bug
Display is strange when exclusive minimum is set

Expected behavior
shows >0

Screenshots
schema

result

Additional context
OpenAPI v3.1
redoc-cli 0.12.3

[miqh]

This isn't a bug with Redoc.

exclusiveMinimum is should be assigned a boolean value—not a numeric one. You should use it in conjunction with the minimum keyword to achieve what you want (i.e. > 0).

https://swagger.io/docs/specification/data-models/data-types/#range

[ivana-isadora]

exclusiveMinimum is should be assigned a boolean value—not a numeric one. You should use it in conjunction with the minimum keyword to achieve what you want (i.e. > 0).

Note that this has changed in OpenAPI 3.1.

Quoting from https://www.openapis.org/blog/2021/02/16/migrating-from-openapi-3-0-to-3-1-0

Tweak exclusiveMinimum and exclusiveMaximum

These two keywords used to take a boolean value, 
which would modify the meaning of the `minimum` and `maximum` properties. 
In OpenAPI v3.1 they are distinct values.

# OpenAPI v3.0
minimum: 7
exclusiveMinimum: true
# OpenAPI v3.1
exclusiveMinimum: 7

The person who reported the issue is using OpenAPI 3.1, so the numeric value should work.