Define formal media type (MIME type) for Swagger Object
See original GitHub issueA media type of application/swagger+json
has been suggested on the mailing list before. I would recommend formally declaring this as part of the spec.
RAML defines its media type as application/raml+yaml
API Blueprint defines its base media type as application/vnd.apiblueprint.ast
plus similar ones for other serializations
Issue Analytics
- State:
- Created 9 years ago
- Comments:88 (55 by maintainers)
Top Results From Across the Web
MIME Types - Swagger
Global MIME types can be defined on the root level of an API specification and are inherited by all API operations. Here the...
Read more >OpenAPI Specification - Version 3.0.3 - Swagger
The OpenAPI Specification defines a standard interface to RESTful APIs which allows ... The media type definitions SHOULD be in compliance with RFC6838....
Read more >OpenAPI Specification - Version 2.0 - Swagger
Version 2.0 specification defines a set of files required to describe an API. These files can then be used by the Swagger-UI project...
Read more >Describing Request Body - Swagger
The body parameter is defined in the operation's parameters section and ... The data type is usually an object, but can also be...
Read more >Swagger RESTful API Documentation Specification
A list of MIME types this operation can produce. This is overrides the global produces definition at the root of the API Declaration....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Considering these:
Optional version parameters:
Version number should only include major and minor. Do not include patch.
Please provide thumbs up on this suggestion?
Following TSC conversation, here is our latest proposal,
Optional version parameter: