Skip to content

Conversation

@glowcloud
Copy link
Contributor

This PR corrects spec paths to schemas in parameters with content, responses and request bodies.

Parameters

parameters:
  - in: query
    name: testestest
    content:
      application/json:
        schema:
          $ref: '#/components/schemas/Pet'

Path to schema before: [..., parameters, 0, schema]
Path to schema after: [..., parameters, 0, content, application/json, schema]

Responses

paths:
  /pet:
    get:
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Pet'

Path to schema before: [content, application/json, schema]
Path to schema after: [paths, /pet, get, responses, 200, content, application/json, schema]

Request bodies

requestBody:
  content:
    application/json:
      schema:
        $ref: '#/components/schemas/Pet'

Path to schema before: [..., content, application/json]
Path to schema after: [..., content, application/json, schema]

@glowcloud glowcloud merged commit 583c4fb into master Oct 17, 2025
8 checks passed
swagger-bot pushed a commit that referenced this pull request Oct 17, 2025
## [5.29.5](v5.29.4...v5.29.5) (2025-10-17)

### Bug Fixes

* **core:** handle complex value stringification in Property component ([#10604](#10604)) ([0422415](0422415)), closes [#10535](#10535)
* correct spec paths for parameters, responses and request bodies ([#10609](#10609)) ([583c4fb](583c4fb))
@swagger-bot
Copy link
Contributor

🎉 This PR is included in version 5.29.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

@glowcloud glowcloud deleted the fix/schema-spec-paths branch October 17, 2025 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants