Fields of format time or date default to "string"

Q	A
Bug or feature request?	Bug
Which Swagger/OpenAPI version?	3.0.1
Which Swagger-Editor version?	Online as of date of post
How did you install Swagger-Editor?	Online
Which broswer & version?	Chrome 63.0.3239.84
Which operating system?	Windows 10

Demonstration API definition

https://gist.github.com/nkolban/fd6aa143ed10af5446fd2950c849e503

Configuration (browser query string, constructor, config.yaml)

Not applicable

Expected Behavior

Here is the example model produced for the operation:

{
  "action": "start",
  "params": {
    "input1": {
      "decimalField": 0,
      "boField": {
        "fieldA": "string",
        "fileB": 0,
        "fieldC": true,
        "anotherBO": {
          "x": "string",
          "y": "string",
          "z": "string"
        },
        "fieldD": [
          "string"
        ]
      },
      "booleanField": true,
      "integerField": 0,
      "timeField": "string",
      "dateField": "string",
      "anyField": "string",
      "stringField": "string"
    }
  }
}

Note the fields called timeField and dateField. These are defined in the JSON Schema as:

       timeField:
          type: string
          format: time
        dateField:
          type: string
          format: date

What I was expecting was that the example fields would be generated as ISO 8601 format strings and not the word string.

For example,

...
      "timeField": "2017-12-09T18:14:01Z",
      "dateField": "2017-12-09",
...

Current Behavior

See above.

Possible Solution

Detect that the field is a date or time format field and generate a default ISO 8601 string based on current time.

Context

Am generating OpenAPI descriptions by interrogating existing servers. Goal is for end user to query server which generates OpenAPI which is then copied into Swagger editor for testing. Generated sample data for the payload of the request should not be the word string.

[nkolban]

Thank you sir. I had misread the time property … what I mean to use was date-time which does appear to be exposed by OAS.

[opendba]

Thank you very much. Everything works as expected!