Optional response codes are not supported

[alex-semenk]

RAML 0.8 specification (https://github.com/raml-org/raml-spec/blob/master/versions/raml-08/raml-08.md#optional-properties) allows to append a question mark ("?") suffix to the name of any non-scalar property to define it as optional in traits and types.

But currently raml parser treat optional response codes as invalid.

Example:

#%RAML 0.8
title: Example of API
traits:
  - SomeTraitName:
      responses:
        200?:
          description: Returned in the case of success.

Actual Result: validation error "Unexpected key '200?'. Options are : /<<(.+?)>>/ or Integer". Expected Result: valid RAML.

Note: Issue present for both 0.8 and 1.0 RAML versions.

Aha! Link: https://mulesoft-roadmap.aha.io/features/APIRAML-105

[eleonoraortega]

Hi @AlexSemenk In Raml 0.8 is correct when defining RESOURCE TYPES and TRAITS

But in raml 1.0 this changed and it is only supported when you defining methods https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md/#declaring-http-methods-as-optional

[RenatEskenin]

This bug is resolved in snapshot versions? In our projects we used ? symbol. How to read raml 0.8 with optional responses?

[mzampare]

Hi, I also would need to have this fixed. Any plans?