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

Only one callback rendered when multiple are defined #9222

Closed
char0n opened this issue Sep 18, 2023 · 1 comment
Closed

Only one callback rendered when multiple are defined #9222

char0n opened this issue Sep 18, 2023 · 1 comment

Comments

@char0n
Copy link
Member

char0n commented Sep 18, 2023

Q&A (please complete the following information)

  • OS: Linux Mint 21.2
  • Browser: Chrome
  • Version: Version 117.0.5938.62 (Official Build) (64-bit)
  • Method of installation: git clone
  • Swagger-UI version: 5.7.1
  • Swagger/OpenAPI version: OpenAPI 3.0.0

Content & configuration

Example Swagger/OpenAPI definition:

openapi: 3.0.0
servers: []
info:
  version: "1.0.0"
  title: home-iot-api
  description: The API
paths:
  /devices:
    get:
      callbacks:
        callbackOne:
          'callbackOne':
            get:
              operationId: callbackOne
              responses:
                '200':
                  $ref: '#/components/schemas/ApiResponse'
        callbackTwo:
          'callbackTwo':
            get:
              operationId: callbackTwo
              responses:
                '200':
                  $ref: '#/components/schemas/ApiResponse'
      tags:
        - Device
      operationId: register
      responses:
        '200':
          description: successfully registered device
components:
  schemas:
    ApiResponse:
      type: object
      properties:
        code:
          type: integer
          format: int32
        message:
          type: string
          example: everything is ok

Describe the bug you're encountering

Only the second callback displays. Expecting to see all the defined callbacks.

To reproduce...

Steps to reproduce the behavior:

  1. npm run dev

Expected behavior

Expecting to see all the defined callbacks.

Screenshots

image

@char0n
Copy link
Member Author

char0n commented Sep 18, 2023

Resolved by #9223

@char0n char0n closed this as completed Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant