Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] invalid types generated (Array & Array<T>;)

See original GitHub issue

@openapitools/openapi-generator-cli: ^1.0.18-4.3.1 openapi: https://solver.314ecorp.tech/openapi?format=json command: node node_modules/@openapitools/openapi-generator-cli/bin/openapi-generator generate -i https://solver.314ecorp.tech/openapi?format=json -g typescript-axios --skip-validate-spec -o ./src/client/generatedApis

Types generated Array & Array<T> for some schema. Here for the 1st type Array there is no generic <T> making problem

/**
 * 
 * @export
 * @interface Unit
 */
export interface Unit {
    /**
     * 
     * @type {string}
     * @memberof Unit
     */
    id?: string;
    /**
     * 
     * @type {string}
     * @memberof Unit
     */
    name?: string;
    /**
     * 
     * @type {number}
     * @memberof Unit
     */
    physiciansToSmeRatioCeiling?: number;
    /**
     * 
     * @type {Array & Array<ApplicationSkill>}
     * @memberof Unit
     */
    requiredApplicationSkillSet: Array & Array<ApplicationSkill>;
    /**
     * 
     * @type {number}
     * @memberof Unit
     */
    usersToSmeRatioCeiling?: number;
}

Issue Analytics

State:
Created 3 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

karthik-hrcommented, Sep 28, 2020

version: 5.0.0-beta2 Array & Array<T> has been changed to Set & Set<T> Typescript compiler expecting generic <T> for Set

ERROR in [at-loader] ./submodules/roster-solver-redux/src/client/generatedApis/api.ts:409:26 
    TS2314: Generic type 'Set<T>' requires 1 type argument(s).

/**
 * 
 * @export
 * @interface Unit
 */
export interface Unit {
    /**
     * 
     * @type {string}
     * @memberof Unit
     */
    id?: string;
    /**
     * 
     * @type {string}
     * @memberof Unit
     */
    name?: string;
    /**
     * 
     * @type {number}
     * @memberof Unit
     */
    physiciansToSmeRatioCeiling?: number;
    /**
     * 
     * @type {Array & Array<ApplicationSkill>}
     * @memberof Unit
     */
    requiredApplicationSkillSet: Set & Set<ApplicationSkill>;
    /**
     * 
     * @type {number}
     * @memberof Unit
     */
    usersToSmeRatioCeiling?: number;
}

1reaction

evergreen-lee-campbellcommented, Jan 12, 2021

If it helps, I faced a similar issue just yesterday to do with the fact that the server itself was generating a definition for Set and Array without actually adding them to the definitions node in the generated JSON schema, because the server was running an old version of Springfox which did not handle Map<> types well. Upgrading Springfox to 3.0.0 on the server resolved the issue.