You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open API Spec as number type and most of the programming language convert into some numeric type(in java it is BigDecimal) which are capable of converting valid number into respective target data type.
@abhiptl this is part of JSON Schema rather than OpenAPI. JSON (and therefore JSON Schema) do not define type conversions or coercions. If you want to use numbers from strings (which is a good way to get around floating point and other limitations of JSON's number type), you use something like "type": "string", "format": "int64" (see the format registry for what formats can be used, and what limitations might be present in support).
Open API Spec as
number
type and most of the programming language convert into some numeric type(in java it is BigDecimal) which are capable of converting valid number into respective target data type.But, open API spec document says below
I want to understand if we should remove above line or that is expectation?
The text was updated successfully, but these errors were encountered: