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 12, 2022. It is now read-only.
/play:
get:
description: Get a collection of <<resourcePathName>>.
responses:
200:
body:
schema: <<resourcePathName>>
example: <<get-example>>
post:
description: Creates a <<resourcePathName | !singularize>>.
body:
schema: <<resourcePathName | !singularize>>
example: <<post-example>>
responses:
201:
description: Successfully created the resource.
/{first}:
uriParameters:
first:
description: |
first parameter
type: string
get:
description: Get a collection of <<resourcePathName>>.
responses:
200:
body:
schema: <<resourcePathName>>
example: <<get-example>>
/subresource:
get:
description: Get a collection of <<resourcePathName>>.
responses:
200:
body:
schema: <<resourcePathName>>
example: <<get-example>>
/{second}:
uriParameters:
second:
description: |
second parameter
type: string
get:
description: Get a collection of <<resourcePathName>>.
responses:
200:
body:
schema: <<resourcePathName>>
example: <<get-example>>
so the url for the for the innermost resource resolves to /play/{first}/subresource/{second}
In this case, the parser does not pick-up the description of the higher level uri parameter and include it in the uri parameter description of the {second} resource.
Also, if I try to manually add the description of the {first} uri parameter in the uriParameter description of the {second} resource in the raml itself, the parser throws a validation error: error validating baseUri, first uri parameter unused.
eg:
/{second}:
uriParameters:
first:
description: |
first parameter
type: string
second:
description: |
second parameter
type: string
Version : 0.8.11
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Consider the following raml document
so the url for the for the innermost resource resolves to /play/{first}/subresource/{second}
In this case, the parser does not pick-up the description of the higher level uri parameter and include it in the uri parameter description of the {second} resource.
Also, if I try to manually add the description of the {first} uri parameter in the uriParameter description of the {second} resource in the raml itself, the parser throws a validation error: error validating baseUri, first uri parameter unused.
eg:
Version : 0.8.11
The text was updated successfully, but these errors were encountered: