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 May 10, 2024. It is now read-only.
API-designer version: 0.0.5
Browser: Chrome version: 44.0.2403.155 (64-bit)
OS: Mac OS X 10.10.5
The RAML 0.8 spec says that "... the value of the named parameter property MAY be an array of mappings ...", with a named parameter defined as "URI parameters, query string parameters, form parameters, request bodies (depending on the media type), and request and response headers".
I can define a named parameter to have multiple types but it does not appear in the documentation preview. Only the first type in the array is shown.
Example - not in error according to the editor panel:
#%RAML 0.8
title: Testing multiple types for named parameters.
/testResource:
get:
queryParameters:
name:
- type: string
description: I am a string type query parameter.
- type: integer
description: I am an integer type query parameter, which is an alternative option.
Documentation shows only the name parameter:
QUERY PARAMETERS
name : string
The text was updated successfully, but these errors were encountered:
API-designer version: 0.0.5
Browser: Chrome version: 44.0.2403.155 (64-bit)
OS: Mac OS X 10.10.5
The RAML 0.8 spec says that "... the value of the named parameter property MAY be an array of mappings ...", with a named parameter defined as "URI parameters, query string parameters, form parameters, request bodies (depending on the media type), and request and response headers".
I can define a named parameter to have multiple types but it does not appear in the documentation preview. Only the first type in the array is shown.
Example - not in error according to the editor panel:
Documentation shows only the name parameter:
QUERY PARAMETERS
name : string
The text was updated successfully, but these errors were encountered: