Open arubalac opened 8 years ago
The correct place to fix this would be https://github.com/mulesoft/raml-object-to-raml, but I'm accepting PRs for functionality that would split up the RAML output. Makes sense to have flags that enables {schemas,examples,resources,traits,resourceTypes}/
directory output, but it's not currently on any roadmap to implement.
Thanks Blake for accepting PR for the functionality.
Hello,
We were able to generate the RAML out of the swagger successfully without any issues but the RAML file generated when loaded to API designer raised error reporting "Request Entity too large" . The reason for this what I understand from mule forum is that the web API designer is having some limitation on the size\length of the file . The currently the size of the RAML is due to the JSON schema represented directly on the RAML file (instead of referencing them).
As of now the only option left out for us is to reduce the size of the RAML which is by segregating the generated JSON schema separated as a file and reducing the overall size of the RAML by just referring them. But this seems to be a tedious task defeating the purpose of accelerating the swagger to RAML conversion.
Could you please suggest or make the appropriate enhancement on the conversion tool.
PFA the RAML generated from the swagger to raml utlity. inventory.zip
Thanks & Regards Arun