Support for anyOf/minProperties for required schema properties.

[tyler-mairose-sp]

Describe the bug

Given the following schema the generated page does not properly render and instead gives an error:

Docusaurus error: the <Tabs> component requires at least one <TabItem> children component

post:
  tags:
  - Suggested Entitlement Description
  operationId: submitSedBatchRequest
  summary: Submit Sed Batch Request
  description: 'Submit Sed Batch Request.

    Request body has one of the following:
      - a list of entitlement Ids
      - a list of SED Ids
    that user wants to have description generated by LLM. 
    API responses with batchId that groups Ids together'
  requestBody:
    description: Sed Batch Request
    content:
      application/json:
        schema:
          description: Sed Batch Request
          type: object
          anyOf:
            - required: [entitlements]
            - required: [seds]
          properties:
            entitlements:
              description: list of entitlement ids
              type: array
              items:
                type: string
                example: 016629d1-1d25-463f-97f3-c6686846650
            seds:
              description: list of sed ids
              type: array
              items:
                type: string
                example: 016629d1-1d25-463f-97f3-c6686846650

Expected behavior

Request body should display and show that you must specific either an array of entitlements or an array of sed ids.

Current behavior

I receive the error above, I believe this is because the plugin is not accounting for this use-case in open api specification.

Possible solution

Steps to reproduce

Create a schema with the use of anyOf property to denote that you must include either property.

Screenshots

Context

Your Environment

• Version used:
• Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3): Node v20.9.0
• Operating System and version (desktop or mobile): MacOS Sonoma 14.7
• Link to your project:

[ahelmy]

Hi @tyler-mairose-sp,
I tested the shared schema and the error is not reproducible, would you check if it is fixed?
Thanks