You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
When an input OAS 2 file includes something of the form examples: <string> when defining a response, the resulting generated RAML 1 output file contains an invalid / fictitious media type '0' .
it'd be preferable if the input was rejected for being an invalid OAS 2 file, or if the invalid examples value was ignored and otherwise output was generated normally.
version of oas-raml-converter where behaviour is observed
observed behaviour
When an input OAS 2 file includes something of the form
examples: <string>
when defining a response, the resulting generated RAML 1 output file contains an invalid / fictitious media type '0' .note, this input OAS 2 file in this scenario appears to be invalid, as the spec states that the examples value should be an object keyed by mime types. in this case, the input has a single string instead of an example object. https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#exampleObject
desired behaviour
it'd be preferable if the input was rejected for being an invalid OAS 2 file, or if the invalid examples value was ignored and otherwise output was generated normally.
version of oas-raml-converter where behaviour is observed
whatever is running currently in https://mulesoft.github.io/oas-raml-converter/ at time of writing
presumably current tip of master?: cadc93e
detail
input format: OAS 2
input content:
output format: RAML 1.0
output content:
The text was updated successfully, but these errors were encountered: