How to handle parameters dynamically?

[caixingyue]

{
  "name": "20240624010101",
  "export_type": "A",
  "filters": {
    "serial_no": "20250624152106683213"
  }
}

I want to dynamically define the key in filters based on the value of export_type. For example, if it is A, the filter can fill in serial_no, as shown in the example above. If it is B, serial_no cannot be filled in, but trade_no can be filled in.

I don't know how to write it in laravel. The closest thing I have is as follows, but there are problems with this result

#[OA\Property(property: 'name', description: 'Task Name', type: 'string', example: '20240624010101')]
#[OA\Property(property: 'export_type', description: 'The is export type', type: 'string', enum: ExportType::class, example: ExportType::TRADE_RECEIPT)]
#[OA\Property(property: 'filters', description: 'The is filters', type: 'object', discriminator: new OA\Discriminator(
        propertyName: 'export_type',
        mapping: [
            'TRADE_RECEIPT' => '#/components/schemas/TradeReceiptFilters',
            'TRANSFER_RECEIPT' => '#/components/schemas/TransferReceiptFilters',
            'FUND_FLOW_RECEIPT' => '#/components/schemas/FundFlowReceiptFilters',
        ]
    ), oneOf: [
            new OA\Schema(ref: '#/components/schemas/TradeReceiptFilters'),
            new OA\Schema(ref: '#/components/schemas/TransferReceiptFilters'),
            new OA\Schema(ref: '#/components/schemas/FundFlowReceiptFilters'),
        ]
    )]

[Onekone]

Discriminators go to schema that have properties that change based on discriminators value, not on properties that depend on that value. In your case it should go to OA\Schema

Oh, and OpenAPI docs say that use of discriminators is preferable for schemas in request bodies and responses. Editor seems to break and hide discriminator property if schema is linked with $ref and not inlined too

[caixingyue]

I'm using this in Laravel. The sample code is from the requester, which I've divided into OA\Schema and OA\Property. For example:

#[OA\Schema]
class test {
    #[OA\Property]
    public function rules()
}

[Onekone]

You put a OA\RequestBody attribute at your class, and write it out in entirety, the hard way, as it would be written in swagger file

#[OA\RequestBody(...)]
#[OA\JsonContent( discriminator: new OA\Discriminator(...), oneOf: [...]]
class test extends FormRequest {
  public function rules() {
    return [
      'export_type' => 'required',
      'filter.trade_no' => 'required_if:export_type,A|prohibited_unless:export_type,A',
      'filter.serial_no' => 'required_if:export_type,B|prohibited_unless:export_type,B'
    ];
  }
}

This library has no magic or explicit support of Laravel and its mechanisms, if that's your question