.Net: Support OpenAPI request body schemas represented by allOf, anyOf and 'oneOf' keywords
#8997
Assignees
Labels
Ignite
Features planned for next Ignite conference
.NET
Issue or Pull requests regarding .NET code
openapi
Issues related to the OpenAPI function importer
sk team issue
A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)
Comments
SergeyMenshykh
added
.NET
github-actions
bot
changed the title
allOf, anyOf and 'oneOf' keywordsallOf, anyOf and 'oneOf' keywords
This was referenced Sep 25, 2024
markwallace-microsoft
added
the
Ignite
markwallace-microsoft
moved this from Backlog: Planned
to Sprint: Planned
in Semantic Kernel
evchaki
added
the
sk team issue
|
Agreed to add samples showing how the API caller can provide a static payload and how LLM can reason over operation schema having allOf, anyOf, oneOf and generate payload to all the operation. |
4 tasks
markwallace-microsoft
moved this from Sprint: Done
to Sprint: In Review
in Semantic Kernel
github-merge-queue bot
pushed a commit
that referenced
this issue
Nov 19, 2024
### Motivation and Context Related to #8997 ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Extend SK OpenAPI functionality to support the
allOf,anyOf, andoneOfkeywords when parsing operation request bodies.In cases where the request body has more than one schema, it should be possible to select which one to use during OpenAPI plugin/function imports. Import filters can be used for that: #6890
The text was updated successfully, but these errors were encountered: