Skip to content

Commit c0cfbea

Browse files
committed
Added clarification for missing formats
Fixes #162
1 parent 163f6e4 commit c0cfbea

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

versions/2.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ Primitive data types in the Swagger Specification are based on the types support
7878

7979
An additional primitive data type `"file"` is used by the [Parameter Object](#parameterObject) and the [Response Object](#responseObject) to set the parameter type or the response as being a file.
8080

81-
<a name="dataTypeFormat"></a>Primitives have an optional modifier property `format`. Swagger uses several known formats to more finely define the data type being used. However, the `format` property is an open `string`-valued property, and can have any value to support documentation needs. Formats such as `"email"`, `"uuid"`, etc., can be used even though they are not defined by this specification. The formats defined by the Swagger Specification are:
81+
<a name="dataTypeFormat"></a>Primitives have an optional modifier property `format`. Swagger uses several known formats to more finely define the data type being used. However, the `format` property is an open `string`-valued property, and can have any value to support documentation needs. Formats such as `"email"`, `"uuid"`, etc., can be used even though they are not defined by this specification. Types that are not accompanied by a `format` property follow their definition from the JSON Schema (except for `file` type which is defined above). The formats defined by the Swagger Specification are:
8282

8383

8484
Common Name | [`type`](#dataTypeType) | [`format`](#dataTypeFormat) | Comments

0 commit comments

Comments
 (0)