types are not in same order as raml file #595

Activity

1. jarrodek commented on Feb 5, 2019

   

   jarrodek

   on Feb 5, 2019

   Contributor

   More actions

   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.
2. pete-lemire commented on Feb 11, 2019

   

   pete-lemire

   on Feb 11, 2019

   Author

   More actions

   Thank you @jarrodek
3. jarrodek

   self-assigned this

   on Feb 13, 2019
4. jarrodek

   added

   3rd party

   on Feb 13, 2019
5. marcadella commented on Apr 24, 2019

   

   marcadella

   on Apr 24, 2019

   More actions

   Same complaint. At least lexicographic ordering is always better than random.
6. jarrodek commented on Apr 26, 2019

   

   jarrodek

   on Apr 26, 2019

   Contributor

   More actions

   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.