Skip to content
This repository has been archived by the owner on Dec 2, 2024. It is now read-only.

Swagger 1.2 Support #30

Open
grahamj opened this issue Jul 25, 2014 · 3 comments
Open

Swagger 1.2 Support #30

grahamj opened this issue Jul 25, 2014 · 3 comments

Comments

@grahamj
Copy link

grahamj commented Jul 25, 2014

ok am I crazy or does swagger-jack not do Swagger 1.2?

@seansylvan
Copy link

It clearly does not support Swagger 1.2, yet as I found out. For example, it expects httpMethod instead of method and "responseClass" instead of "type" in the api object, "dataType" instead of "type" in the param object, and "date" instead of "dateTime" as data type.

It would be real nice to have a support for Swagger 1.2.

@grahamj
Copy link
Author

grahamj commented Sep 11, 2014

Ya I wasted a lot of time finding that out. Now I use swagger-tools, much better.

@seansylvan
Copy link

one more thing about 1.1 versus 1.2:
In the definition of complex data type, 1.2 has a separate required section:

"User": {
      "id": "User",
      "required": [
        "phone",
        "email",
      ],
      "properties": {
        "phone": {
          "type": "string"
        },

and 1.1 has the required field of entries within the properties object:

"User": {
      "id": "User",
      "properties": {
        "phone": {
          "required": true,
          "type": "string"
        },

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants