[Question] Can Swagger generate custom generic types?

[MelnikovIG]

Assume we have API return model in C#

public class ApiResult<T>
{
  public T Result;
  public bool Success;
}

and returning ApiResult<string> object instance to client

so we have swagger generated model

ApiResult[String] {
  result (string, optional),
  success (boolean, optional)
}

which is incorrectly converted to typescript class using https://swagger.io/swagger-codegen/

'use strict';
import * as models from './models';
export interface ApiResultString {
    result?: string;
    success?: boolean;
}

Is it possible to generate output models with generics same as in input models?

[Pangamma]

Bump

[HugoMario]

i'm not so familiar with typescript, but if you guys conclude that this is the best practice, we can implement it.

[mauropanzeri]

I agree with the opening post.
Generally ApiResult is a generic wrapper from the real payload from the rest backend.

At this moment if you have n APIs that all wraps n different objects, you end having ApiResultObjectApi1... ApiResultObjectApi2... ApiResultObjectApiN in the generated code.
Several useless repetition that serves a "difficult" to use api.service.ts

Since typescript supports generics, it would be ideal to generate the typescript interfaces as generics as well. The code that use those could be more generic and the models would be DRY and smaller.

[mauropanzeri]

A little more thinking into this and i just realized that there is an indecision case.

Suppose a c# mode like this

public class ApiResult<T>
{
  public T Result;
  public bool Success;
  public string message;
}

and an api returning ApiResult<string> object instance to client

so we would have swagger generated model

ApiResult[String] {
  result (string, optional),
  success (boolean, optional)
  message (string, optional)
}

how the generator's template should behave?
It doesn't know which of the strings are from the generics.

Maybe a typescript-angular generate's option like enableGenerics (default: false) should be better. so you can enable it only iff you're sure of the api's model.

[Pangamma]

Yes, the spec needs to be updated to handle this case. Otherwise, a generator would need a minimum of two types being used in a generic result before it could decide which properties are generic and which properties are stationary.

[robbertvanhove]

Hi, is there any progress on supporting generics in TypeScript yet? Thanx!

[bluoxy]

I have a same problem.

[Savrov]

I wish to use this feature too

[fendorio]

Same

[Bernix01]

Any update on this?

[Pangamma]

2021 says hello. I still need and want this feature. (Also seems to be my third time finding this issue via Google. )

[rhopiCoder]

+1

[Thomas-Lederer]

+1

[damien7792]

+1

[ShuuMakengi]

+1

[joshuafc]

+1

[fadi-shahoud]

+1

[barta-home]

Same here

[joshuafc]

2022 says hello. I still need and want this feature.

[duaneking]

Bumping for fix

[m17kea]

Would love to see this implemented

[josemariabaena]

i have the same problem . is is available?

[davethieben]

2023 says, siighhh.... still open...

[Chgocn]

I wish to use this feature too

[ullfindsmit]

+1

[GaffaRay]

Great feature to implement.

[sabine19]

+1

[Junad-Park]

still open...

[Aweptimum]

It's possible to document generics in a spec through dynamic references (henry andrews approved), but I don't think swagger-codegen supports them

[Alamonall]

Hello! Any progress?