While Rapidoc renders "int64" for the path parameters (which seems fine as int64 implies integer type), it shows "integer" for the response object property (see the following screenshot, type information marked green):
This is confusing, as the user will assume that the parameter and property have different data types, which is not the case.
Data type information should be rendered uniformly including format details in all places.
The representation of data types is inconsistent for path parameters and response objects:
In the following sample OpenAPI, a path parameter and a response object property are both defined with
type:integer
andformat:int64
.Sample OpenAPI:
While Rapidoc renders "int64" for the path parameters (which seems fine as int64 implies integer type), it shows "integer" for the response object property (see the following screenshot, type information marked green):
This is confusing, as the user will assume that the parameter and property have different data types, which is not the case. Data type information should be rendered uniformly including format details in all places.