Type Members

1.  class CleanIdenticalExamples extends TransformationStep
2.  class CleanNullSecurity extends TransformationStep
3.  class CleanParameterExamples extends TransformationStep
4.  class CleanRepeatedOperationIds extends TransformationStep
5.  class DeclareUndeclaredSecuritySchemes extends TransformationStep
6.  class FixConsumesAndProduces extends TransformationStep

   Contrary to OAS, In RAML, mediaTypes defined in requests/responses bodies are not added to the field accepts/contentType of the model So in the MediaTypeResolutionStage, when converting from RAML to OAS 2.0, the accepts and contentType only include the global mediaType (if defined).

   Contrary to OAS, In RAML, mediaTypes defined in requests/responses bodies are not added to the field accepts/contentType of the model So in the MediaTypeResolutionStage, when converting from RAML to OAS 2.0, the accepts and contentType only include the global mediaType (if defined). This led to some inconsistent transformations when mediaTypes were defined in bodies as accepts/contentType did not correlate to the payload's mediaTypes. The purpose of this step is to address this issue. To do this, mediaTypes are collected from payloads and accepts and contentType fields are set with that values. This way payload's mediaTypes and modified fields will correlate, solving the inconsistency. The only particular case is when a file parameter is defined inside the request body. The accepts field is filled with the 2 possible mediaTypes according to the spec.

7.  class LowercaseSchemes extends TransformationStep
8.  class MandatoryDocumentationUrl extends TransformationStep
9.  class MandatoryPathParameters extends TransformationStep
10.  class MandatoryResponses extends TransformationStep
11.  class Oas20SecuritySettingsMapper extends SecuritySettingsMapper