-
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. The file I created to start with ha…
-
When applying libraries some people get confused and think they have to use the include keyword.
See these questions on stack overflow:
http://stackoverflow.com/questions/42427263/mulesoft-error…
woodp updated
7 years ago
-
The specification could be an RFC, W3C recommendation or any other kind of document. Two APIs with same specification can be accessed the same way (e.g. with the same client library). The human readab…
-
We need a top level functional specification which is testable. Harnessing it up to (e.g.) [Selenium](http://www.seleniumhq.org/) will not be easy, but even if we don't get an automated test framework…
-
Proposal: Use Problem JSON as an error response format.
Problem is a standardized way of describing any kind of error thrown by an API. The advantage on using a standardised format is that any syst…
-
`oas-raml-coverter version 1.1.35`
The OAS parser used by [ReDoc](https://github.com/Rebilly/ReDoc) project complains about a forbidden definition:
``` text
Error: Incompatible types in allOf …
jsamr updated
5 years ago
-
Hi.
I'm working on a particular use case: generating stand-alone type declarations not using any user introduced type names.
This is useful in situations where you cannot keep the name-to-declaration…
-
Add support to specify different examples on resources based on input values: uri parameter, query parameters, headers, etc.
A naif proposal:
``` yaml
#%RAML 1.0
title: PoC on examples including inp…
-
Specification v 0.8 requires parsers to interpret JSON Schema and XML schema. This does not prevent usage of other schema types (e.g. RELAX NG inXML or compact form).
The questions are:
- is this exp…
-
Consider following example:
``` yaml
/files:
get:
responses:
200:
body:
application/json:
type: files.File
post:
responses:
200:
body:
…