Use of oneOf for schemas problematic for SDK

[emigun]

Summary

Using oneOf in openAPI schema makes it impossible to create an instance of some classes in the SDK.

Steps to Reproduce

Using DatasetsControllerFindByIdAndUpdateRequest in the python SDK as an example:

from scicat_sdk_py.models.datasets_controller_find_by_id_and_update_request import DatasetsControllerFindByIdAndUpdateRequest

instance = DatasetsControllerFindByIdAndUpdateRequest.from_dict({"principalInvestigator": "Emil"})

Current Behaviour

This raises a ValueError.

Expected Behaviour

An instance should be created.

Details

The following error is raised:
ValueError: Multiple matches found when deserializing the JSON string into DatasetsControllerFindByIdAndUpdateRequest with oneOf schemas: PartialUpdateDerivedDatasetObsoleteDto, PartialUpdateRawDatasetObsoleteDto.

It is my understanding that oneOf should be used in cases where it strictly is one of the schemas. For us this doesn't work because there is overlap between the Dtos (actually they are almost identical).

In our case, anyOf is probably better?

oneOf is used for four endpoints in the datasets controller.

[Junjiequan]

We will investigate this issue asap