The MuleSoft API Designer reports an
undefined alias when an
*alias reference precedes the
&alias definition. Otherwise the file is syntactically correct.
Isn’t one of the design features of RAML that the order of the elements is unimportant? And doesn’t the (apparent) requirement that an alias definition precede all any reference to it break this goal? (Just sorting members in a properties map, can now break a correct definition.)
Or is this a misunderstanding on my part?