mulesoft / osprey

Generate Node.JS API middleware from a RAML definition
Other
431 stars 66 forks source link

Support Level 2 URI templates #88

Open dmartinezg opened 8 years ago

dmartinezg commented 8 years ago

The following RAML is not supported:

#%RAML 0.8
title: Sample API
/files:
  /{+fileName}:
    uriParameters:
      fileName:
        type: string
        pattern: ^.*$
    get:

What I would expect from osprey is to be able to make a GET on /files/some/arbitrary/fileName

RAML 0.8 omits saying that Level 2 is not available to use in uriParameters, so I would assume, that tooling should be able to handle this with a flag, somehow.

WDYT?

blakeembrey commented 8 years ago

Unfortunately, the RAML specification is explicit about Level 1 support only - see https://github.com/raml-org/raml-spec/issues/73 for the issue raised on the public specification.