opengeospatial / ogcapi-processes

Home Page:https://ogcapi.ogc.org/processes

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

transmissionMode and response default value definitions

gfenoy opened this issue · comments

In the following schemas, the default value is defined as a list of a single value rather than the value itself:

  • core/openapi/schemas/execute.yaml
  • core/openapi/schemas/transmissionMode.yaml

In consequence, the Example Value produced by the swagger-ui is as below (see it live from here):

{
  "inputs": {
    "additionalProp1": "string"
  },
  "outputs": {
    "additionalProp1": {
      "format": {
        "mediaType": "string",
        "encoding": "string",
        "schema": "string"
      },
      "transmissionMode": [
        "value"
      ]
    }
  },
  "response": [
    "raw"
  ],
  "subscriber": {
    "successUri": "string",
    "inProgressUri": "string",
    "failedUri": "string"
  }
}

By defining the default value as a string rather than a list of a single string, the Example Value looks like the following (see it live from here:


{
  "inputs": {
    "additionalProp1": "string"
  },
  "outputs": {
    "additionalProp1": {
      "format": {
        "mediaType": "string",
        "encoding": "string",
        "schema": "string"
      },
      "transmissionMode": "value"
    }
  },
  "response": "raw",
  "subscriber": {
    "successUri": "string",
    "inProgressUri": "string",
    "failedUri": "string"
  }
}

I think that this last produced Example Value from swagger-ui is correct.

This issue was solved by the #277 PR. Note that this fix applies for the current approved version.