API Helper

A tool to help developers in generating code for interfaces, classes, objects, form templates, and more.

English | 简体中文

A versatile tool library for building Web APIs and code templates

• 🎉️ Supports openapi2, openapi3.0, openapi3.1, yapi interface documents, and custom interface document parsing
• 💪 Built with Typescript
• ⚙️ Unit testing
• 💻 Local deployment

📄 API Generation

Usage CLI

Examples

$ npx apih -u http://your-api-documentation-address.com
# or
$ npx apih -u ./local-openapi.json

Usage: apih [options]
Options:
  -u, --url <string> Interface document address [Can read local files when type is 'swagger', here can be a local file path]
  -o, --output-path <path> Output path after code generation
  --target <string> Generated target code type, default: typescript
  --type <string> Interface document type, call the built-in parser according to the document type, default value: 'swagger'
  --auth-token <string> Accessing documents may require authentication information, accessed through using token, yapi's validation token

Usage config in file

Initialize Configuration File

Enter the following command to initialize the configuration file.

$ npx apih init

Command Description

Usage: apih init [options]
Options:
  -c, --config-path <path> Custom configuration file path.

Execute to generate API

• Open the apih.config.js or apih.config.ts file for configuration.
• After completing the configuration, enter the following command to generate the API.

$ npx apih 

Command Description

Usage: apih [options]
Options:
  -c, --config-path <path> Custom configuration file path.

apih.config.ts

import type { Config } from '@api-helper/cli';
import { defineConfig } from '@api-helper/cli';

defineConfig accepts a Config object or Config[]. When you need to generate multiple API files, you can use the array method. The following document is a supplementary explanation of the Config object.

import { defineConfig } from '@api-helper/cli';

export default defineConfig({
  // Use group function. After enabling this function, multi-file code will be generated according to the group
  group: false,
  // Whether to generate only the TypeScript type of interface request data and return data. If yes, the request file and request function will not be generated.
  onlyTyping: false,
  // The output path after code generation
  outputPath: 'src/api/index.ts',
  // The target type of the generated code. Default: typescript
  target: 'typescript',
  // File path of the request function.
  requestFunctionFilePath: 'src/api/request.ts',
  // Set all fields of the request data as required attributes, default: false
  requiredRequestField: false,
  // Set all fields of the response data as required attributes, default: true，默认：true
  requiredResponseField: true,
  // Interface document service configuration
  documentServers: [{
    // Interface Document address [When the type below is 'swagger', you can read local files, here can be a local file path]
    url: 'http://your-api-documentation-address.com',
    // Interface document type, call the built-in parser according to the document type, default value: 'swagger' [Built-in yapi and swagger parser, other document types, add parserPlugins to implement document parsing by yourself]
    type: 'swagger',
    // The name of the current interface document service. When there is a value, the file output becomes -> path/current name
    name: '',
    // The key to get the response data, body[dataKey]
    dataKey: '',
    // Accessing the document may require authentication information, which can be done using HTTP auth type.
    auth: {
      username: '',
      password: '',
    },
    // Accessing the document may require authentication information, which can be accessed using a token, such as Yapi's authentication token.
    authToken: '',
    // Request headers when fetching the interface document with AJAX.
    headers: {},
    // Hook events in the execution process.
    events: {
      // Event callback when generating interface name, the return value is used as the new InterfaceName, which is used to customize the InterfaceName.
      // onRenderInterfaceName(api, options) {},
      // Event callback when generating API name, the return value is used as the new RequestFunctionName, which is used to customize the RequestFunctionName.
      // onRenderRequestFunctionName(api, options) {},
    },
  }],
  // Parse extension plugins, used for custom parsing
  parserPlugins: [],
});

📦 Web Service

Web services provide custom code generation based on interfaces and provide frontend operation pages to make code generation more convenient.

• The application scenario of WEB services is repetitive form or table pages, generating unified code templates according to the interface.
• The WEB service function is essentially a product of the B/S architecture and needs to be deployed locally.
  • The browser-side code is under the web package.
  • The server-side code is under the server package.

Deployment document

For Windows environment, please install pnpm first, and then double-click to run the run-web-server.bat file. The following are manual deployment steps.

Step 1: Download the project code.

Download or use git to pull the entire project code.

git clone https://github.com/ztz2/api-helper.git

Step 2: Packaging.

• To package the browser code, go to the web package, and enter the command: pnpm run build.
• To package the server-side code, go to the server package, and enter the command: pnpm run build.

Step 3: Start the service.

• To start the service, go to the server package, and enter the command: pnpm run start:prod.
• After the service starts, visit the address: http://localhost:3210.
• If you need to run the latest code, you need to start from step 1. The subsequent service start-up operations are all step 3.

👏 Sponsors

Thanks to JetBrains for supporting this project.

📃 LICENSE

MIT Copyright (c) 2023-present, ztz2