fix: add nullable condition to multipart formdata for openapi3.1

[kosa3]

Status

READY

Description

OpenAPI 3.1 introduces support for jsonschema's 'null' type, however,
there is a problem in multipart/formdata where the generated code does not correctly determine null.
Specifically, the expected output from the following yaml is different.

https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00#section-7.6.1

input.yaml

openapi: '3.1.0'
info:
  version: 1.0.0
  title: Swagger Petstore
paths:
  /pets:
    post:
      summary: Create a pet
      operationId: createPets
      tags:
        - pets
      requestBody:
        content:
          multipart/form-data:
            schema:
              type: object
              properties:
                name:
                  type: [ string, 'null' ]
      responses:
        '204':
          description: Created Pet

• Expected

if(createPetsBody.name !== undefined && createPetsBody.name !== null) {
 formData.append('name', createPetsBody.name)
 }

• Generated

if(createPetsBody.name !== undefined) {
 formData.append('name', createPetsBody.name)
 }

Related PRs

List related PRs against other branches:

branch	PR
other_pr_production	link
other_pr_master	link

Todos

• Tests
• Documentation
• Changelog Entry (unreleased)

Steps to Test or Reproduce

Outline the steps to test or reproduce the PR here.

> git pull --prune
> git checkout <branch>
> grunt jasmine

[soartec-lab]

@kosa3
nice update!
Would you add a test case using this below?

• https://github.com/orval-labs/orval/blob/master/tests/configs/default.config.ts

[soartec-lab]

@kosa3
I added a comment.

[soartec-lab]

It's okay to use an existing schema 👍

https://github.com/orval-labs/orval/blob/master/tests/specifications/null-type.yaml#L41-L48

[kosa3]

Thanks, I fixed it.
I also found a bug when oneOf, anyOf, allOf subschemas are attached and fixed it.

[soartec-lab]

it's good. I added some updated comments. Once you fix that, it's perfect!

[soartec-lab]

Thanks for good work !