Order of operations in the API specification file vs Azure Developer Portal API reference #2623
Replies: 3 comments
-
|
Hello @hemchander23 , the order of the API's operations is ordered by name (which is the summary field from the spec ) and this is by design. We currently don't have in plan to change this. |
Beta Was this translation helpful? Give feedback.
-
|
I'm having this same problem too and would really like to change the order without having to alphabetize the summaries of each endpoint. I can kind of see why this might have been the design, to group List, Create, Update resources, but in practicality, those verbs don't match up with the actual functionality of many endpoints. It looks messy. |
Beta Was this translation helpful? Give feedback.
-
|
Just adding another voice here... this is a terrible way to sort things. Especially since my preference is to display the URL paths by default rather than the summaries. The sort order in that case looks even more random. IMO, if you're defaulting to URL paths being displayed instead of summaries, it should at least sort by URL path in that case. |
Beta Was this translation helpful? Give feedback.
-
Bug description
The operations listed in the Azure Developer Portal - API Reference view is in a different order compared to the one in the API specification file.
For instance: This is how it looks in Swagger Editor with the same ordering of operations as they are in the spec. file. However once it is uploaded, it seems to change to a different one. My guess is that it is now based on the operation summary?
Reproduction steps
Expected behavior
Maintain the ordering as specified in the API spec. file.
Is your portal managed or self-hosted?
Managed
Release tag or commit SHA (if using self-hosted version)
N.A
API Management service name
N.A
Environment
Additional questions:
Beta Was this translation helpful? Give feedback.
All reactions