swagger-api / swagger-api/swagger-codegen

can I use path property instead property name in request body in descriminator ?

Open
#10,094 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

`My question is:
can I use path property instead of property name in request body for descriminators like:

pet:
type: object
oneOf:
- $ref: "#/components/schemas/dog"
discriminator:
pathProperty: type
mapping:
dog: "Dog"
dog:
allOf:
- $ref: "#/components/schemas/pet"
- type: object
required:
- type
properties:
type:
type: string`

Swagger-codegen version

3.0.18

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the discriminator and request-body example in the issue against Swagger Codegen 3.0.18 and the OpenAPI behavior it targets. Determine whether a pathProperty option is supported or define the required scope before identifying an implementation location and validation approach.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.