Customizing the ordering of "tags" (whole sections of the API, e.g. "Dataset" or "Dataset search") is possible by adding a Java bean. This alters the ordering of the content in the OpenAPI schema output.
However, methods are children of paths, so while it would be possible to rearrange paths in the schema output, it's not possible to rearrange each method. We can have:
GET /dataset/{key}
PUT /dataset/{key}
DELETE /dataset/{key}
GET /dataset/search
...
but we cannot have
GET /dataset/{key}
GET /dataset/search
PUT /dataset/{key}
DELETE /dataset/{key}
...
Ordering like that would need to be done in the Javascript UI. I think the methods could still be tagged with an extension to define the ordering.
Customizing the ordering of "tags" (whole sections of the API, e.g. "Dataset" or "Dataset search") is possible by adding a Java bean. This alters the ordering of the content in the OpenAPI schema output.
However, methods are children of paths, so while it would be possible to rearrange paths in the schema output, it's not possible to rearrange each method. We can have:
but we cannot have
Ordering like that would need to be done in the Javascript UI. I think the methods could still be tagged with an extension to define the ordering.