You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2024. It is now read-only.
The resource type has to optional methods, a post and a delete, both of which attempt to define a parameters in the body of a request (createAuthority and deleteAuthority respectively). But the example defines these properties directly in the body property, which is invalid.
Per the the spec:
A method's body is defined in the body property as a hashmap, in which the key MUST be a valid media type.
Presumably the authors meant these parameters to be form parameters, as they are defined within a body. If that is the case, then they should have been defined under the formParameters property, which in turn should be under one of the two web form media types as keys in the body property.
E.g.
#%RAML 0.8title: Example of Optional PropertiesresourceTypes:
- auditableResourcepost?:
body:
application/x-www-form-urlencoded:
formParameters:
createAuthority:
description: | If the resource has a post method defined, expect a createAuthority property in its bodydelete?:
body:
multipart/form-data:
formParameters:
deleteAuthority:
description: | If the resource has a delete method defined, expect a deleteAuthority property in its body
The text was updated successfully, but these errors were encountered:
The example resource type ins the Resource Types and Traits / Optional Properties section is invalid.
The resource type has to optional methods, a post and a delete, both of which attempt to define a parameters in the body of a request (createAuthority and deleteAuthority respectively). But the example defines these properties directly in the body property, which is invalid.
Per the the spec:
Presumably the authors meant these parameters to be form parameters, as they are defined within a body. If that is the case, then they should have been defined under the formParameters property, which in turn should be under one of the two web form media types as keys in the body property.
E.g.
The text was updated successfully, but these errors were encountered: