.Net Bug: OpenAPI descriptions with parameters defined under the path item are ignored

[calebkiage]

Describe the bug According to the OpenAPI spec, parameters are allowed under the path object and should apply to all operations under that path item. Semantic Kernel currently only uses parameters under the operation object.

An example OpenAPI:

{
  "openapi": "3.0.3",
  "info": {
    "title": "Test Schema",
    "version": "0"
  },
  "servers": [
    {"url": "https://localhost:3000"}
  ],
  "paths": {
    "/users/{userId}": {
      "get": {
        "operationId": "getUserById",
        "responses": {
          "default": {
            "description": ""
          }
        }
      },
      "parameters": [
        {
          "name": "userId",
          "in": "path",
          "required": true
        }
      ]
    }
  }
}

Expected behavior Semantic kernel should consider path item parameters as well as operation parameters when building a plugin

Platform

• OS: Windows
• IDE: VS Code
• Language: C#
• Source: main branch of repository

Additional context

[markwallace-microsoft]

Hi @calebkiage thanks for creating this issue. Is this a blocking issue for you and if yes, can you provide some detail on the impact to help us to prioritise this.

[calebkiage]

Hi @markwallace-microsoft, it's not a blocking issue. I'm cataloguing gaps in semantic kernel's OpenAPI support and opening issues for tracking.

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity.