Description

Issue

When rendering OpenAPI schemas with allOf containing multiple oneOf or anyOf items, the nested schemas were not rendering properly. The schema merge operation was losing or combining the separate constraint arrays instead of preserving them as independent options.

Example Schema Pattern

This issue affected schemas like:

allOf:

Constraint 1: Must be one of these policy types

• oneOf:
  • security-rule-type
  • internet-rule-type
    discriminator: ...

Constraint 2: Must exist in one of these scopes

• oneOf:
  • folder
  • snippet
  • deviceIn this pattern, the object must satisfy one option from each oneOf group (multiple independent constraints), but only one oneOf was rendering or they were incorrectly merged together.

Affected Operations

• Create a security rule (POST /security-rules) in examples/httpbin.yaml
• Any schema using allOf with multiple oneOf/anyOf constraints

Root Cause

The SchemaNode component was using mergeAllOf() for all allOf schemas, which flattens multiple oneOf arrays into a single merged result. This loses the independence of each constraint.

Solution

Modified packages/docusaurus-theme-openapi-docs/src/theme/Schema/index.tsx:

1. Detect multiple choice constraints: Check if allOf contains more than one oneOf or anyOf item
2. Preserve independence: Render each oneOf/anyOf constraint separately as its own tabbed interface
3. Merge for shared properties: Still merge the schema to extract shared properties, which are rendered after the constraints
4. Maintain backward compatibility: Standard allOf merge behavior is preserved for schemas without multiple choice constraints

Rendering Order

• First: All oneOf/anyOf constraints (each as tabbed options)
• Then: Shared properties that apply to all combinations

Changes

• Modified packages/docusaurus-theme-openapi-docs/src/theme/Schema/index.tsx
• Added test case POST /allof-multiple-oneof in demo/examples/tests/allOf.yaml

Testing

The fix has been tested with:

• The original security-rules schema from httpbin.yaml
• A new comprehensive test case in allOf.yaml demonstrating:
  • Two independent oneOf constraints (type selection + scope selection)
  • Shared properties across all combinations
  • Proper tab rendering for each constraint
  • Property visibility based on selected options

Screenshots

Before

Only one oneOf was visible, or constraints were incorrectly merged

After

Both oneOf constraints render as separate tabbed interfaces, followed by shared properties