[BUG] Pydantic generator does not correctly handle nullable union

[janne-slamcore]

Describe the bug.

The following spec:

{
  title: 'NullableUnionTest',
  type: 'object',
  required: ['nullableUnionTest'],
  properties: {
    nullableUnionTest: {
      anyOf: [
        {
          title: 'Union1',
          type: 'object',
          properties: {
            testProp1: {
              type: 'string'
            }
          }
        },
        {
          type: 'null'
        }
      ]
    }
  }
};

generates the following Pydantic model:

class NullableUnionTest(BaseModel): 
  nullableUnionTest: Union[Union1] = Field()
  additionalProperties: Optional[dict[Any, Any]] = Field(default=None)

which does not allow the null/None value.

Expected behavior

The generated model should support null/None values.

Screenshots

How to Reproduce

1. Clone https://github.com/janne-slamcore/modelina/tree/pydantic-nullable-union
2. Undo change to Pydantic.ts
3. npx jest test/generators/python/

🥦 Browser

None

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[jonaslagoni]

@janne-slamcore go for it ✌️

[jonaslagoni]

@janne-slamcore there is also quite a bit of fixes to python in the next branch in case you encounter more, check it out ✌️