DEV Community: little-jenney

Quickly-Code-Toolkit: A Powerful Tool to Boost Development Efficiency

little-jenney — Wed, 12 Feb 2025 07:58:21 +0000

Product Introduction

Code-Toolkit is a practical tool developed based on IntelliJ IDEA, integrating functions of rapid code generation and SQL statement auxiliary generation. It can quickly create various files such as controller.java, provider.java, and service.java, and rapidly write methods into the corresponding files. Additionally, it can generate SQL ALTER and CREATE TABLE statements based on class definitions, enabling developers to focus on business logic development.

Usage Instructions

Global Settings

Paging Wrapper Setting: Used for paging wrapping of return parameters when writing methods. You need to set the fully qualified name, for example, com...Page. Example: public Page testMethod(){}.
View Wrapper Setting: This is the wrapper class for parameters returned to the front - end page when writing methods. Set the fully qualified name, such as com...CommonResponse. Example: public CommonResponse> testMethod(){}.
ORM Framework Setting: Used for template selection when creating dao.java, service.java, and serviceImpl.java files. The templates for MyBatis and MyBatis - Plus are different.
Remote Invocation Framework Setting: Used for template selection when creating files and writing methods. Dubbo is used to create provider files and write methods; OpenFeign is used to create Controller files and write methods.

Creation of Business Logic Files

Directory Rules: The parent directory of business logic files is based on the SpringApplication directory. The mapper.xml file is created in the resources/mapper directory.

Creation Methods:

Creation from Database Source Table Structure: Select the table structure in the database section of the IDEA navigation bar, then right - click and select 【Database To Business Logic】.
Entity Class Creation: You can select an entity class in the left - hand project directory or within the entity class code, then right - click and select 【Entity To Business Logic】.
Writing Business Logic Methods
Writing Scope: Supports various files such as mapper.xml and dao.java.
Writing Rules: For files like dao.java, the methods are written automatically. For controller or provider, the selection is based on the remote invocation setting. For mapper.xml, the writing depends on whether the XML method is selected.
Usage Steps: Right - click on the corresponding file and select 【Method To Business Logic】, then select the parameters.
SQL Auxiliary Functions
Function Purpose: Generate ALTER statements for newly added fields in an entity class and CREATE TABLE statements for newly added entity classes.
Type Correspondence: Java data types generally correspond to MySQL data types. Special types need to be manually modified.
Usage Steps:
Generate ALTER Statements: Select a field, right - click, and select 【Class Member To SQL】.
Generate CREATE TABLE Statements: You can select an entity class in the left - hand project directory or within the code, then right - click and select 【Class To SQL】.

Contact Information

GitHub Issue: GitHub - little - kelp/code - toolkit
Email: sunflower.on.sun@gmail.com
QQ Group: 1030094275

Still typing code manually? This amazing tool will skyrocket your development speed!

little-jenney — Mon, 10 Feb 2025 08:23:46 +0000

Are you troubled by the tedious process of creating code files and writing SQL statements during Idea code development? Do you spend a great deal of time each time you create files like controller.java and service.java, or write SQL? Don't worry, Quickly - Code - Toolkit is here to save the day!
This powerful tool is built on the foundation of the Idea code development IDE and is specifically designed to boost development efficiency. It comes with two core functions, making it an efficiency accelerator for developers.
Rapid Code Generation
Previously, creating files such as controller.java, privder.java, service.java, dao.java, and mapper.xml required manual operations one by one, which was time - consuming and labor - intensive. Now, with Quickly - Code - Toolkit, you can generate these files with just one click. Moreover, it can quickly write methods into the corresponding files, saving you a huge amount of time and energy and freeing you from the cumbersome repetitive work.
Assisted SQL Statement Generation
When it comes to database operations, Quickly - Code - Toolkit also shines. It can quickly generate alter statements based on the fields of a class or directly generate create table statements from a class. You no longer have to wrack your brains over complex SQL statements, which greatly improves the efficiency of database operations.
By using Quickly - Code - Toolkit, you can devote more time and energy to the development of business logic code and focus on the core business, making your development work much easier and more efficient.
Don't hesitate any longer. Search for 【Quickly - Code - Toolkit】 in the Idea Marketplace right away and embark on your high - efficiency development journey!

Quickly - Code - Toolkit, a tool for quickly generating Java code in Idea

little-jenney — Sun, 09 Feb 2025 03:14:16 +0000

Introduction to Quickly - Code - Toolkit

Quickly - Code - Toolkit is a tool based on the Idea code - development IDE, which realizes the functions of [quick code generation] and [assisted SQL statement generation]. Code - Toolkit can assist us in development by quickly [creating files such as controller.java, provider.java, service.java, dao.java, and mapper.xml], quickly writing methods into [controller.java, provider.java, service.java, dao.java, mapper.xml, etc.], and rapidly [generating ALTER statements for adding fields to a class or CREATE TABLE statements for a class], thus improving efficiency and enabling us to focus more on business - logic code development. You can search for [Quickly - Code - Toolkit] in the Idea marketplace.

Instructions for Using Code - Toolkit

I. Global Settings

1. Paging Wrapper Setting (Paging Settings)

Explanation 1: It is mainly used for writing methods and serves as a paging wrapper class for return parameters.
Explanation 2: The setting method is the fully qualified name of the paging wrapper class: com...Page.
Explanation 3: Example of return parameter - public Page testMethod(){}

2. View Wrapper Setting (Return Front - End Page Parameter Wrapper Settings)

Explanation 1: It is mainly used for writing methods and is a wrapper class for parameters returned to the front - end page.
Explanation 2: The setting method is the fully qualified name of the return front - end parameter wrapper class: com...CommonResponse.
Explanation 3: Example of return parameter: public CommonResponse testMethod(){}

3. ORM Framework (orm Framework Settings)

Explanation 1: It is mainly used for selecting file - creation templates for dao.java, service.java, and serviceImpl.java files. The file - creation templates for Mybaits and Mybatis - plus are different.

4. Remote Invocation Framework (Remote Invocation Settings)

Explanation 1: It is mainly used for selecting templates during file creation and writing methods.
Explanation 2: The Dubbo Framework is mainly for creating provider files and writing methods into provider files.
Explanation 3: Openfeign is mainly used for creating Controller files and writing methods into controller files.

II. Creation of Business - Logic Files

Explanation 1: The parent directory of the business - logic file directory is based on the directory of the SpringApplication. For example, if the directory of SpringApplication is /src/java/com/test, then the directory of Entity is: /src/java/com/test/entity/Entity.
Explanation 2: The mapper.xml file is created under the resources directory, and the default file directory is mapper. For example, src/resources/mapper//EntityMapper.xml.
Explanation 3: The way to create files from the database source table structure includes creating entity.java, mapper.xml, dao.java, service.java, serviceImpl.java, controller.java, or provider.java (for Dubbo) files.
Explanation 4 - Steps for [Creating Files from the Database Source Table Structure]:
a. Select the database in the Idea side navigation bar.
b. Select the table structure, such as the activity table.
c. Right - click and select the [Database To Business Logic] button.
Explanation 5: The scope of business - logic files created from an entity class includes mapper.xml, dao.java, service.java, serviceImpl.java, controller.java, or provider.java (for Dubbo) files.
Explanation 6 - Steps for [Creating Business - Logic Files from an Entity Class]:
Method 1:
a. In the left - hand side project directory.
b. Select the entity class for which you want to create business - logic files.
c. Right - click and select the [Entity To Business Logic] button.
Method 2:
a. Select within the code of the entity class for which you want to create business - logic files.
b. Right - click and select the [Entity To Business Logic] button.

III. Business - Logic Methods

Explanation 1: Methods are written into files such as mapper.xml, dao.java, service.java, serviceImpl.java, controller.java, or provider.java (for Dubbo).
Explanation 2: Methods are automatically written into dao.java, service.java, and serviceImpl.java. For controller or provider (Dubbo) files, it depends on the [Remote Invocation Framework] to decide whether to write into the controller or provider. Writing into mapper.xml depends on whether an xml method is selected.
Explanation 3: The paging of methods and the packaging of return - page parameters are set respectively in Paging Wrapper Setting (Paging Settings) and View Wrapper Setting (Return Front - End Parameter Wrapper Settings).
Explanation 4: It supports writing methods starting from files such as dao.java, service.java, serviceImpl.java, controller.java, or provider.java (for Dubbo) to other files. For example, when writing a method in the mapper.java file, it will also write to mapper.xml, service.java, serviceImpl.java, controller.java, or provider.java (for Dubbo) files.
Explanation 5 - Steps for Use: In mapper.xml, dao.java, service.java, serviceImpl.java, controller.java, or provider.java (for Dubbo) files, right - click [Method To Business Logic] and select the required parameters.

IV. SQL Assistant Functions

Explanation 1: The SQL assistant functions are used to generate ALTER statements for adding fields to an entity class and CREATE TABLE statements for adding an entity class to generate a table structure.
Explanation 2: Since Java data types and MySQL data types do not have a one - to - one correspondence, only a basic general correspondence can be achieved. For example, for a status (1\2\3) that uses Integer in Java, the generated MySQL SQL statement uses the int type for reception, and the tinyint type in MySQL cannot be used. If you want to change the type, it needs to be modified manually.
Explanation 3 - Steps for [Generating ALTER Statements for Table Structure Fields]:
a. Select the field for which you want to generate the ALTER statement.
b. Right - click and select the [Class Member To SQL] button.
Explanation 4 - Steps for [Generating CREATE TABLE Statements for Table Structure]:
Method 1:
a. In the left - hand side project directory.
b. Select the entity class for which you want to create business - logic files.
c. Right - click and select the [Class To SQL] button.
Method 2:
a. Select within the code of the entity class for which you want to create business - logic files.
b. Right - click and select the [Class To SQL] button.

EMAIL: sunflower.on.sun@gmail.com
github issue:【https://github.com/little-kelp/code-toolkit】
QQ Group: 1030094275
Odd - numbered versions are for Idea version 242.* and below. Even - numbered versions are for versions above 242. (excluding 242.)