Function name generation may be misleading/incorrect

[lionel87]

I had issues with the function name generation, a path like /user/logout generated as api.user.logoutList() but it is not actually a list.
A different path like /clients/{zone} is generated as api.clientsDetail() which is actually a list.

It would be a good feature to give control over the naming, or use the naming scheme that the swagger.io generator uses. it suffixes the name with the http method, like api.user.logoutGET() and api.clientsGET().

The current behavior that checks if the path contains placeholders are working only on simple or example apis I quess.

swagger-typescript-api/templates/base/route-name.ejs

Line 18 in b0fab0d

_.camelCase(`${pathName}_${hasPathInserts ? "detail" : "list"}`),

swagger-typescript-api version: 13.0.12

[snuup]

This is very serious. WIthout any reason my api method "getBunny" is renamed into "getBunnyList". Makes no sense at all.

[petr-jilek]

You can create your template for your project.

For example, you can create the templates folder in your project and add the mentioned route-name.ejs file to this folder.

In this file templates/route-name.ejs you can create custom behavior. For example update the methodAliases part like:

const methodAliases = {
  get: (pathName, hasPathInserts) => _.camelCase(`${pathName}_get`),
  post: (pathName, hasPathInserts) => _.camelCase(`${pathName}_post`),
  put: (pathName, hasPathInserts) => _.camelCase(`${pathName}_put`),
  patch: (pathName, hasPathInserts) => _.camelCase(`${pathName}_patch`),
  delete: (pathName, hasPathInserts) => _.camelCase(`${pathName}_delete`),
};

Then in your command specify the template folder path. For example:

swagger-typescript-api -p http://localhost:5000/swagger/v1/swagger.json -o ./api -n api.ts -t ./templates

I tried it only with this file in the templates folder and it worked.