This sort of depends on #2 - the RAML spec allows the transformation functions "pluralize" and "singularize". This should behave similarly with #2 where the actual resource that inherits a parameterized type/trait overwrites the <<parameterFoo>> as well as takes care of the transform functions, like <<parameterFoo | !pluralize>> turns into someFoos (rather than someFoo.
This sort of depends on #2 - the RAML spec allows the transformation functions "pluralize" and "singularize". This should behave similarly with #2 where the actual resource that inherits a parameterized type/trait overwrites the
<<parameterFoo>>
as well as takes care of the transform functions, like<<parameterFoo | !pluralize>>
turns intosomeFoos
(rather thansomeFoo
.