Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identical inline request schema share a name #24

Open
jtreminio opened this issue Mar 12, 2025 · 0 comments
Open

Identical inline request schema share a name #24

jtreminio opened this issue Mar 12, 2025 · 0 comments

Comments

@jtreminio
Copy link
Owner

Given

openapi: 3.1.0
info:
  version: 1.0.0
  title: Fixture - Property Examples
tags:
  - name: pet
  - name: some_other
paths:
  /operation_1:
    post:
      tags:
        - pet
      operationId: operation_1
      requestBody:
        content:
          application/json; charset=utf-8:
            schema:
              type: object
              properties:
                labels:
                  type: array
                  description: Array of labels (comma-separated strings)
                  items:
                    type: string
        required: true
      responses:
        '200':
          description: Successful operation
  /operation_2:
    post:
      tags:
        - some_other
      operationId: operation_2
      requestBody:
        content:
          application/json; charset=utf-8:
            schema:
              type: object
              properties:
                labels:
                  type: array
                  description: Array of labels (comma-separated strings)
                  items:
                    type: string
        required: true
      responses:
        '200':
          description: Successful operation

the name for both inline schema in requestBody share the same name.

It might be Operation1Request or Operation2Request. Need to figure this one out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant