importing RAML and Swagger definition provides 2 different behaviours

[lucamaf]

While importing RAML automatically generates an application plan, swagger import doesn't and using the relative argument '-a' doesn't help

[picsoung]

Thanks @lucamaf for the feedback.
Really likely that they have different behavior, as RAML has been supported as a proof of concept more than a feature.

But if there is demand it can be improved.

[lucamaf]

i think unless we plan to actually include a GUI / API tool to the API manager, the CLI tool will be used more and more, so would like to ask you to improve in the sense of my comment if possible

[picsoung]

with Mulesoft joining the OpenAPI Initiative , RAML usage will decrease, I believe.

To fully support RAML we need actual numbers/facts telling that there are X customers that use RAML exclusively...
Not supporting it upfront is a chance to have a conversation about OpenAPI, and help them making a move to a more common API description format.