types are not in same order as raml file

[pete-lemire]

[jarrodek]

Hi,
Thank you for issue report.
API console iterates over the array of declarations found in the AMF model (see here: https://github.com/advanced-rest-client/api-navigation/blob/stage/api-navigation.html#L747). Then it iterates over list of references to do the same (references are external files like fragments containing among others RAML types). There's no sorting function used in navigation. I will bring this issue onto attention of AMF team to see if this can be fixed in the AMF model.

[pete-lemire]

Thank you @jarrodek

[marcadella]

Same complaint. At least lexicographic ordering is always better than random.

[jarrodek]

According to AMF team types are actually in right order. It might get weird when you apply external types and / or libraries. I am not sure myself how this is exactly processed but the console also includes types from external sources in navigation and it may produce some unexpected results in terms of ordering. However the console use the order defined in AMF model.