IssueTracker

Let's say I have the following operation in my OpenAPI specification with a 200 response and a default response describing the error format (standard usage for the feature according to https://swagger.io/docs/specification/2-0/describing-responses/):
{
  "description": "Updates a category in the library (reset not specified fields).",
  "operationId": "CategoryV1CategoryUpdateCategoryDefinition",
  "parameters": [
    {
      "$ref": "#/components/parameters/securityCode"
    },
    {
      "$ref": "#/components/parameters/domain"
    }
  ],
  "responses": {
    "200": {
      "description": "A successful response",
      "content": {
        "application/json": {
          "schema": {
            "$ref": "#/components/schemas/ApiCategoryDefinition"
          }
        }
      }
    },
    "default": {
      "description": "A failed response",
      "content": {
        "application/json": {
          "schema": {
            "$ref": "#/components/schemas/GoogleJsonErrorContainer"
          }
        }
      }
    }
  },
  "requestBody": {
    "$ref": "#/components/requestBodies/ApiCategoryDefinition"
  }
}

In Endpoints Portal, I would expect the default response to be displayed at the end of the response list (like in most Swagger UI variants). Instead, the default response is displayed first, which does not really make sense for an error.