Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Standardize the way models (complex typed) are referred #32

Closed
webron opened this issue Apr 7, 2014 · 1 comment
Closed

Standardize the way models (complex typed) are referred #32

webron opened this issue Apr 7, 2014 · 1 comment

Comments

@webron
Copy link
Member

webron commented Apr 7, 2014

The way we refer to model (complex) types is different between model (complex) type declarations, container declarations and Operation Object declarations. Normally, the field $ref is used, but in the case of Operation Object the field type is used. In Response Message Object the field responseModel is used. We should go with single variation for this, probably the $ref one to conform with JSON-Schema.
@webron webron mentioned this issue Apr 7, 2014
Closed
fehguy added a commit that referenced this issue Sep 8, 2014
@fehguy
Merge pull request #32 from fehguy/master
a57e4b8 
added form data parameter schema, tests
@webron
Copy link
Member Author

webron commented Sep 19, 2014

This has been resolved in Swagger 2.0.

@webron webron closed this as completed Sep 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@webron