Open APIs

Hello,

We are working with the TMF OpenAPI specification and we have some struggle when using a code generator with inheritance. Since the swagger does not specify the @type field as required, nor does specify a discriminator, we need to do some configuration to generate code using inheritance rather than combining the fields from the classes.

Is anyone aware of the rationale behind the decision of not using discriminator in the TMF entities?

Hi Martin

In the Open APIs up to and including v4, we were using Swagger 2.x - and for various reasons (admittedly I'm not so familiar with the details) it wasn't feasible to make this part of the API definitions.

In v5 APIs (first batch of APIs soon to be released) we have upgraded to OAS 3.x , including extensive use of oneOf, and @type is used as a discriminator for inheritance.

Hope it helps

Hello,

We are working with the TMF OpenAPI specification and we have some struggle when using a code generator with inheritance. Since the swagger does not specify the @type field as required, nor does specify a discriminator, we need to do some configuration to generate code using inheritance rather than combining the fields from the classes.

Is anyone aware of the rationale behind the decision of not using discriminator in the TMF entities?

Thanks @Jonathan Goldberg, it helps a lot as we were afraid doing it on existing contracts would break something unexpectedly. 

We'll move ahead with our cusotmization while waiting for v5 release.

Hi Martin

In the Open APIs up to and including v4, we were using Swagger 2.x - and for various reasons (admittedly I'm not so familiar with the details) it wasn't feasible to make this part of the API definitions.

In v5 APIs (first batch of APIs soon to be released) we have upgraded to OAS 3.x , including extensive use of oneOf, and @type is used as a discriminator for inheritance.

Hope it helps

Hello,

We are working with the TMF OpenAPI specification and we have some struggle when using a code generator with inheritance. Since the swagger does not specify the @type field as required, nor does specify a discriminator, we need to do some configuration to generate code using inheritance rather than combining the fields from the classes.

Is anyone aware of the rationale behind the decision of not using discriminator in the TMF entities?