Qoder CN Series:Extension management

For Enterprise Dedicated Edition, Qoder CN admins and global admins can manage commands and control access in Extension of the Qoder CN console. Authorized developers with command access can type / to invoke these commands.

Manage commands

View commands

Qoder CN admins and global admins can view default and custom commands in the Extensions section of the console.

The extension management page provides a search box and a Create Command button at the top. Use the All, Custom Commands, and Official Commands tabs to filter commands. Each command card shows its name, description, user count, and enabled or disabled status.

Click a command card to view its details, access control, and usage.

Create commands

To create a command, click Create Command in Extensions.

Step 1: Enter basic information

• Name: 1–64 characters. Supports letters, numbers, underscores, and spaces. Displayed to developers when they type / in Qoder CN. Use a clear, consistent naming format.

• Description: Explain the command's purpose. Maximum 200 characters.

• Icon: Select an icon and color for the command.

• Access control:

  • Public: Members authorized to access Qoder CN

  • Private: Members authorized to access the commands

Step 2: Configure command details

For example, in Prompt, define the system prompt and output format requirements for a code naming task, such as list length and naming rules. In Context, set both #userInput and #selectedCode to Required, and define an assembly template such as "Generate variable names for #selectedCode based on the requirements in #userInput". After configuration, click Create Now.

• Prompt: Up to 5,000 characters. Define the system identity and requirements.

• Context: Select contexts such as #userInput and #selectedCode. Developers can access these by typing # in Qoder CN.

• Chat History: When enabled, the command includes chat history as context.

Manage access control

Manage access control on the command details page.

• For a public command, click View under Access Control to see authorized developers.

• For a private command, click View under Access Control to add or remove authorized developers.

Enable or disable commands

Test the command before rolling it out to all users:

1. Change the command access to Private.

2. Add only testers to the list.

3. Turn on the switch to enable the command.

4. Testers can then test the command in the Qoder CN.

After testing, configure access control as needed.

To disable a command, turn off its switch. The command no longer appears in the / command list.

Modify commands

On the command details page, click Modify in the upper-right corner to edit the command.

Delete commands

To delete a command, click Delete in the upper-right corner. This action is irreversible.

Use commands

Developers with access can invoke commands by typing / in Qoder CN's chat box.

The command list displays built-in commands, such as /explain code, /generate unit test, and /generate comment, as well as custom commands, such as /dao and /generate api docs.

Examples

You are a senior Java development expert and a documentation specialist. Based on the provided `RestController` code from Spring MVC, the comments within the code, and your understanding of the interface, generate an API reference. Use the following template:

Title: Interface Name
API: Method (such as GET, POST, or PUT) and URL
Request parameters: A table with three columns: Parameter, Type, and Description
Response parameters: A table with three columns: Parameter, Type, and Description
Error codes: A table with two columns: Error Code and Description