-
It is quite common to see APIs describing some of their methods, resources and even parameters as being deprecated. This is currently done via text in the description field.
-
In order to support JSONP a new `jsonp` property should be added to methods. This property MUST be interpreted in the following way:
- If present in a method, this operation can be called using JSONP
…
-
_Originally documented here:_
https://github.com/mulesoft/api-designer/issues/203
In the case of traits, the rules are:
1. If the property is in the resource/method, then this will be the final valu…
-
Different users of RAML types have different (and usually opposed) of describe the information of the type at the syntactical level.
Users authoring RAML documents would favor:
- compact and expressi…
-
The following raml has types with the same name in the root raml and the dependent libraries that is passed as a resource type parameter.
Which would be the final types of headers hA, hA2, hB, hB2?
…
-
Currently the RAML spec is just used for documentation purposes, without any connection to the real code. This has given problems1 and will keep giving problems. Either we should drop it (I wouldn't s…
-
Could we get support for something like F#'s type providers in the future?
Let me present some use case scenarios for this.. Let's suppose you have a TS project trying to access a REST API, and this …
-
I really like your theme, IMHO the biggest missing feature is the cURL commands.
-
it would be grate to generate RAML automatically on /doc endpoint, for example.
-
This is related to #256, but applies to consecutive slashes created between resources.
If an API has a convention of using trailing slashes on resources, then it's unclear how RAML expects that to be…