ozonophore/openapi-codegen

A simple library that generates TS-interface models from openapi specification

openapi-codegen's Issues

No option to choose the query interface: cancelable or simple

You must be able to choose whether the query interface is canceled or simple. You need to add a cli parameter to select the interface.

Models are incorrectly generated if the path B to the specification in the Ref parameter is indicated using "../".

If the specification specifies the refine in this way $ref: ../openapi_example/viewExampleDto.yml. Then the generation of models occurs in another directory above.
This violates the integrity of the structure of the generated directory and models.

The problem is still relevant. It's not enough to remove the jump to the directory above. The issue has been identified in model paths, model imports, and schema imports.

Enum with value

According to specification, an enum can contain only name, values are situated in a description.
Example:

schema:
type: string
enum: [asc, desc]
description: >
Sort order:
* asc - Ascending, from A to Z
* desc - Descending, from Z to A

Add cancelable concept

Need to add cancelable concept. This will allow you to correctly cancel requests and handle further scripts.

Generate and export path & method for operation

Generated paths can be useful for stabbing in tests
Example

interface IConfig {
    path: string;
    method: 'post' | 'delete' | 'get'
}

export const serviceConfig = (baseUrl: string): IConfig => {
    return {
        getUser: {
            path: `${baseUrl}/users`,
            method: 'get',
        }
        getUsersById: {
            path: `${baseUrl}/users/:id`,
            method: 'get',
        },
    }
};

in test:

const config = getServiceConfig('rest/v1');

const configForGetUser = config['getUser'];
export const handler = rest[configForGetUser.method](configForGetUser.users, (_, res, ctx) => {
    return res(ctx.status(200));
})

Add embedded support axios

Models are incorrectly generated if the path B to the specification in the Ref parameter is indicated using "../".

If the specification specifies the refine in this way $ref: ../openapi_example/viewExampleDto.yml. Then the generation of models occurs in another directory above.
This violates the integrity of the structure of the generated directory and models.

It doesn't maintain generation classes in subfolders. So the name of the class can be very long and unusability.

$ref can contain a link to a component in an external file

Example:

$ref: ./file.yaml#/components/AnyComponent

I expect that generator will create an interface AnyComponent in the models folder

Delete word 'type' from template witch is using in an import and export block

Describe the solution you'd like
A clear and concise description of what you want to happen. Ideally with a small example of the proposed changes.

Add support Date-type

Describe the solution you'd like
A clear and concise description of what you want to happen. Ideally with a small example of the proposed changes.

This is an incorrect path in a block of import in Windows

Provide the ability to set OpenApi configuration parameters in request files.

Actual result: OpenApi configuration is hardcoded. There is no way to manually specify parameters - BASE, VERSION, WITH_CREDENTIALS, TOKEN, USERNAME, PASSWORD, HEADERS.

Expected result: in the custom request file you can specify the OpenApi configuration for further use.

Add support divided directories for each groups models, core, schemas, and services

Add parameters to config:

• outputCore
• outputModels
• outputSchemas
• outputServices