api-designer
api-designer copied to clipboard
A web editor for creating and sharing RAML API specifications
Currently, the API designer is only able to import files from a ZIP or Swagger Spec. To further enhance usability, it would be nice to also be able to import...
Taking the discussion on issue #369 in consideration, it might be a good idea to integrate a documentation tool like [raml2html](https://github.com/kevinrenskers/raml2html) or [php-raml2html](https://github.com/mikestowe/php-raml2html) into the API Designer. Perhaps through a...
**Note:** All this features are WIP. **New Layout** **Scope** **Extract to** ![extractto](https://cloud.githubusercontent.com/assets/302314/10490334/e0a224ec-7276-11e5-834f-714c0a36b424.gif) **Search** - Search for resources - Search for text - Navigate though lines - Search for files ![search](https://cloud.githubusercontent.com/assets/302314/10490336/e1caf592-7276-11e5-8b3d-db44ba7027ef.gif)
When the number of !included examples is high is difficult to find the actual file. It would be nice to be able to cmd+click (or similar) the !include file line...
Can anyone share some details as how we can deploy API Designer to a tomcat container.
RAML files should be able to be cached and the cached state retrieved from memory through an `!include`. This would improve performance of parsing large sets of RAML files.
With large files, it would be much easier to work if the editor defaulted everything to a collapsed state so I can then just expand the pieces I'm actively working...
I noticed that the Resources view (the dynamic and interactive api explorer on the right) does not always show up. It seems to be linked with creating a new file....
adding sugar query param
Addresses basic auth not working (issue #217)