Correct value parsing <<resourcePathName>>


I have found that two different tools from Mule Soft resolve the paramenter resourcePathName.

In this simple example:

#%RAML 0.8
title: documents-api
version: 0.1

  - item:
      description: Entity representing a <<resourcePathName|!singularize>>


API Designer resolves the variable to “document”, but API Workbench resolves it to “id”. Which one is the correct, according to the spec?

If it’s the second case, how could I include “document” in the description?


<<resourcePathName|!singularize>> should resolve to document


Seems to be a bug, I’ve raised an issue here