CN116679912A - Code generation method, apparatus, device, storage medium, and computer program - Google Patents

Abstract

The application discloses a code generation method, device, equipment, storage medium and computer program, belonging to the field of computer technology. The method includes: acquiring the business logic code of the target application and at least one appearance code of the target application under the target development framework, determining the non-rendering code of the target application under the target development framework based on the business logic code, and determining the non-rendering code of the target application under the target development framework and at least one appearance code to obtain the complete code of the target application under the target development framework. Since the at least one appearance code indicates at least one appearance of the target application, and the at least one appearance corresponds to at least one type of terminal, the finally obtained complete code can ensure that the target application is compatible with the target development framework, It can also ensure that the appearance of the target application can adapt to different terminal devices.

Description

Code generation method, device, equipment, storage medium and computer program

Technical Field

The present application relates to the field of computer technology, and in particular to a code generation method, apparatus, device, storage medium and computer program.

Background Art

JavaScript ("JS" for short) is a lightweight, interpreted or just-in-time compiled programming language with function-first behavior. This language is widely used in the development of world wide web (Web) applications.

In the process of Web application development, in order to improve the efficiency of code writing, technicians usually use JS-based development frameworks to design Web applications, such as Vue, React, etc. However, when designing Web applications, the Web application code written by technicians includes business logic code and appearance code, but because Web applications usually need to adapt to different terminal devices such as mobile phones and computers, and the appearance of Web applications corresponding to different terminal devices is different. In this case, for Web applications with the same business logic, technicians need to repeatedly write the code for Web applications for different terminals so that the Web applications have an appearance that is compatible with the terminal devices. This will cause technicians to spend a lot of time writing code, which greatly increases labor costs and time costs.

Summary of the invention

The present application provides a code generation method, apparatus, device, storage medium and computer program, which can solve the problem of low efficiency of application development in related technologies. The technical solution is as follows:

In a first aspect, a code generation method is provided, the method comprising: obtaining a business logic code of a target application and at least one appearance code of the target application under a target development framework, the business logic code indicating a function of the target application, the at least one appearance code indicating at least one appearance of the target application, the at least one appearance corresponding to at least one terminal type; determining a rendering-free code of the target application under the target development framework based on the business logic code; and organizing the rendering-free code and the at least one appearance code to obtain a complete code of the target application under the target development framework.

By obtaining the business logic code of the target application and at least one appearance code of the target application under the target development framework, the complete code of the target application under the target development framework is determined based on the business logic code and the at least one appearance code. Since the at least one appearance code indicates at least one appearance of the target application, and the at least one appearance corresponds to at least one terminal type, the complete code can ensure that the target application is compatible with the target development framework while also ensuring that the appearance of the target application can adapt to different terminal devices. In other words, the code generation method provided in the present application can automatically generate the complete code of the target application under the target framework, without the need for technicians to repeatedly write the code for the target application for different terminals and different development frameworks, thereby greatly improving the efficiency of code writing and effectively saving manpower and time costs.

There are multiple implementation methods for obtaining the business logic code of the target application and at least one appearance code of the target application under the target development framework, and two of them are introduced below.

In the first implementation method, the cloud platform can display a code writing interface, which is used to write the business logic code of the target application and at least one appearance code of the target application under the target development framework. In response to the code writing completion operation, the cloud platform can obtain the business logic code of the target application and at least one appearance code of the target application under the target development framework.

In the second implementation method, the technicians can complete the writing of the business logic code and the at least one appearance code of the target application on other cloud platforms with code writing functions, and then send the business logic code and the at least one appearance code of the target application to the cloud platform, and the cloud platform receives the business logic code and the at least one appearance code of the target application.

That is, the business logic code of the target application and the at least one appearance code can be obtained directly after being written by the technician on the cloud platform, or can be sent to the cloud platform after being written by the technician on other cloud platforms with code writing functions. Of course, in actual applications, the cloud platform can also obtain the business logic code of the target application and the at least one appearance code in other ways.

Optionally, the business logic code is in the form of a curried function, and the business logic code and the at least one appearance code are in JavaScript language.

The rendering-free code of the target application under the target development framework can be determined by following the steps (1)-(2) below.

(1) Determine the function name of at least one logic function in the business logic code, the parameter name of at least one parameter corresponding to the at least one logic function, and the attribute name of each parameter in the at least one parameter.

The business logic code includes logic code comments and logic code body. In this case, the function name of the at least one logic function can be obtained from the logic code body, and the parameter name of at least one parameter corresponding to the at least one logic function and the attribute name of each parameter can be obtained from the logic code comments.

The cloud platform can determine a first position from the business logic code body, where the code at the first position contains the function name of the at least one logic function, and obtain the function name of the at least one logic function from the code at the first position.

The cloud platform stores a first string. In this case, the cloud platform can search for the first string from the business logic code according to the relevant algorithm, determine the location of the first string as the first location, and use the code at the first location except the first string as the function name of at least one logical function.

It should be noted that, in actual applications, the first string can also be determined by other means. For example, the technician can also input the first string in the cloud platform so that the cloud platform can obtain the first string. When the technician inputs the first string, the cloud platform can display the first string input interface, complete the operation in response to the first string input, and obtain the first string input by the technician.

Based on the above description, the function name of the at least one logic function can be determined by the cloud platform from the business logic code body. In practical applications, the function name of the at least one logic function can also be determined by other means. For example, a technician can directly input the function name of the at least one logic function in the cloud platform so that the cloud platform can obtain the function name of the at least one logic function.

In order to facilitate the cloud platform to identify the logic code annotation, the format of the logic code annotation is a target format. In this case, the cloud platform stores the target format in advance, and the cloud platform can determine the parameter name of at least one parameter and the attribute name of at least one parameter corresponding to at least one logic function from the logic code annotation according to the target format and the relevant algorithm.

(2) Based on the function name of the at least one logic function, the parameter name of the at least one parameter, the attribute name of each parameter in the at least one parameter, and the storage path of the business logic code, the rendering-free template corresponding to the target development framework is filled to obtain the rendering-free code of the target application under the target development framework.

The non-rendering template corresponding to the target development framework includes a first area to be filled, and the first area to be filled includes a logic function import sub-area, a logic code path sub-area, an initialization sub-area, an API object creation area, a mount and update area, and an API object created area. In this case, the function name of the at least one logic function can be written into the logic function import sub-area, the storage path of the business logic code can be written into the logic code path sub-area, the parameter with the target attribute name in at least one parameter is used as the first parameter, and the target attribute name indicates that the parameter with the target attribute name is a data model, and the initialization sub-area is filled based on the first parameter, and the parameter name of the first parameter and the function name of the first logic function in at least one logic function are written into the API object creation area, and the first logic function is a logic function without a target parameter name, and the target parameter name indicates that the logic function with the target parameter name is an interface function. If there is a mount function in at least one logic function, the code of the function name of the mount function under the target framework is written into the mount and update area. The function names of the logic functions other than the first logic function in at least one logic function are written into the API object created area to achieve the filling of the non-rendering template corresponding to the target development framework.

The implementation process of filling the initialization sub-area based on the first parameter includes: determining the initialization code of the first parameter in the target framework, and writing the initialization code into the initialization sub-area.

The cloud platform stores the correspondence between the target attribute name and the initialization code under the target framework. Based on the attribute name included in the first parameter that is the same as the target attribute name, the initialization code of the first parameter under the target framework can be determined from the correspondence between the target attribute name and the initialization code under the target framework.

It should be noted that the above target attribute name, target parameter name and function name of the mount function are set in advance. The target attribute name can be set to model, the target parameter name can be set to api, and the function name of the mount function can be set to mounted. Of course, in actual applications, the target attribute name, target parameter name and function name of the mount function can also be set to other names.

In actual applications, before filling in the non-rendering template corresponding to the target development framework, the cloud platform needs to determine the target development framework. In this case, the cloud platform can display a development framework selection interface, which is used to select the target development framework. In response to the development framework selection completion operation, the cloud platform can determine the target development framework. That is, after the cloud platform displays the development framework selection interface, the technician can select a development framework as the target development framework in the development framework selection interface. After the selection is completed, the technician can trigger the development framework selection completion operation. In response to the development framework selection completion operation, the cloud platform determines the target development framework.

Since there are multiple development frameworks, different development frameworks have different ways of obtaining the complete code of the target application under the target development framework. Next, the corresponding implementation methods of two of the development frameworks are introduced.

In the first case, the target development framework is the Vue framework, the target application is a Web application, the target application includes at least one component, and the at least one appearance code indicates at least one appearance of the at least one component. In this case, based on the at least one appearance code, the component name of the subcomponent contained in the at least one component and the attribute name of the at least one component can be determined, and based on the attribute name of the at least one component, the component name of the subcomponent and the storage path of the non-rendering code, the code adaptation template corresponding to the target development framework is filled to obtain the complete code of the target application under the target development framework.

Each appearance code in the at least one appearance code includes an appearance code comment. In this case, the component name of the subcomponent in the at least one component and the attribute name of the at least one component can be obtained from the appearance code comment.

In order to facilitate the cloud platform to identify the appearance code annotation, the format of the appearance code annotation is a target format. In this case, the cloud platform stores the target format in advance, and the cloud platform can determine the component name of the subcomponent in the at least one component and the attribute name of the at least one component from the appearance code annotation according to the target format and the relevant algorithm.

Optionally, the target format is jsdoc format. Of course, the format of the logic code comment can also be other types of formats.

The code adaptation template corresponding to the target development framework includes a second area to be filled, and the second area to be filled includes a non-rendering code path sub-area, a component attribute sub-area, and a sub-component sub-area. In this case, based on the attribute name of at least one component, the component name of the sub-component contained in at least one component, and the storage path of the non-rendering code, the implementation process of filling the code adaptation template corresponding to the target development framework includes: writing the storage path of the non-rendering code into the non-rendering code path sub-area, writing the attribute name of at least one component into the component attribute sub-area, and filling the sub-component sub-area based on the component name of the sub-component contained in at least one component.

Optionally, a subcomponent filling code template is stored in the cloud platform, and the subcomponent filling code template includes a name area and a path area. In this case, based on the component name of the subcomponent contained in at least one component, the implementation process of filling the subcomponent subarea includes: for any subcomponent contained in at least one component, the component name of the subcomponent is written into the name area of the subcomponent filling code template, and the storage path of the complete code of the subcomponent is written into the path area of the subcomponent filling code template to obtain the filling code corresponding to the subcomponent. For each subcomponent contained in at least one component, the filling code corresponding to each subcomponent can be obtained in the same manner, and the filling code corresponding to each subcomponent is written into the subcomponent subarea to achieve the filling of the subcomponent subarea.

In order to facilitate technical personnel to improve the development efficiency and code quality of applications, the target development framework also has corresponding tool library codes. In this case, the code adaptation template corresponding to the target development framework also includes a tool library path sub-area, and the cloud platform can write the storage path of the tool library code corresponding to the target development framework into the tool library path sub-area.

In the second case, the target development framework is the React framework, the target application is a Web application, the target application includes at least one component, and the at least one appearance code indicates at least one appearance of the at least one component. In this case, the attribute name of the at least one component can be determined based on the at least one appearance code, the function name of at least one logic function in the business logic code can be determined, and the code adaptation template corresponding to the target development framework can be filled based on the attribute name of the at least one component, the function name of the at least one logic function, and the storage path of the non-rendering code, so as to obtain the complete code of the target application under the target development framework.

Each of the at least one appearance code includes an appearance code body, or includes an appearance code body and an appearance code comment. When the appearance code includes the appearance code body, the attribute name of at least one component is obtained from the appearance code body; when the appearance code includes the appearance code body and the appearance code comment, the attribute name of at least one component is obtained from the appearance code body or the appearance code comment.

The cloud platform may determine a second position from the appearance code body, where the code at the second position includes the attribute name of the at least one component, and obtain the attribute name of the at least one component from the code at the first position.

Optionally, the cloud platform stores a second string. In this case, the cloud platform can search for the second string from the appearance code body according to a relevant algorithm, determine the location of the second string as the second position, and use the code at the second position except the second string as the attribute name of at least one component.

It should be noted that, in actual applications, the second string can also be determined by other means. For example, the technician can also enter the second string in the cloud platform so that the cloud platform can obtain the second string. When the technician enters the second string, the cloud platform can display the second string input interface, and in response to the second string input completion operation, obtain the second string entered by the technician. For example, the cloud platform can display the second string designation interface, and the technician can enter the second string in the second string designation interface. After the input is completed, the technician can trigger the second string input completion operation. In response to the second string input completion operation triggered by the technician, the cloud platform obtains the second string entered by the technician.

Based on the above description, the attribute name of the at least one component can be determined by the cloud platform from the appearance code body. In actual applications, the attribute name of the at least one component can also be determined by other methods. For example, a technician can directly input the attribute name of the at least one component in the cloud platform so that the cloud platform can obtain the attribute name of the at least one component.

The code adaptation template corresponding to the React development framework includes a third area to be filled, and the third area to be filled includes a non-rendering code path sub-area, a component attribute sub-area, and a logic function sub-area. In this case, based on the attribute name of the at least one component, the function name of the at least one logic function, and the storage path of the non-rendering code, the implementation process of filling the code adaptation template corresponding to the target development framework includes: writing the storage path of the non-rendering code into the non-rendering code path sub-area, writing the attribute name of at least one component into the component attribute sub-area, and writing the function name of at least one logic function into the logic function sub-area.

In order to facilitate technical personnel to improve the development efficiency and code quality of applications, the target development framework also has corresponding tool library codes. In this case, the code adaptation template corresponding to the target development framework also includes a tool library path sub-area, and the cloud platform can write the storage path of the tool library code corresponding to the target development framework into the tool library path sub-area.

In a second aspect, a code generation device is provided, wherein the code generation device has the function of implementing the code generation method in the first aspect. The code generation device includes at least one module, and the at least one module is used to implement the code generation method provided in the first aspect.

In a third aspect, a computing device cluster is provided, the computing device cluster comprising at least one computing device, each computing device comprising a processor and a memory, the processor of the at least one computing device being used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the code generation method provided in the first aspect above.

Optionally, each computing device may further include a communication bus, which is used to establish a connection between the processor and the memory of each computing device.

In a fourth aspect, a computer-readable storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a computing device cluster, the computing device cluster executes the steps of the code generation method described in the first aspect.

In a fifth aspect, a computer program product comprising instructions is provided. When the instructions are executed on a computing device cluster, the computing device cluster executes the steps of the code generation method described in the first aspect.

The technical effects obtained by the above-mentioned second, third, fourth and fifth aspects are similar to the technical effects obtained by the corresponding technical means in the first aspect, and will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of a code generation method provided by an embodiment of the present application;

FIG2 is a schematic diagram of a code writing interface provided in an embodiment of the present application;

FIG3 is a schematic diagram of another code writing interface provided in an embodiment of the present application;

FIG4 is a schematic diagram of a first character string specifying interface provided in an embodiment of the present application;

FIG5 is a schematic diagram of a non-rendering template corresponding to a Vue framework provided in an embodiment of the present application;

FIG6 is a schematic diagram of a non-rendering template corresponding to another Vue framework provided in an embodiment of the present application;

FIG7 is a schematic diagram of a non-rendering template corresponding to a React framework provided in an embodiment of the present application;

FIG8 is a schematic diagram of a non-rendering template corresponding to another React framework provided in an embodiment of the present application;

FIG9 is a schematic diagram of a development framework selection interface provided in an embodiment of the present application;

FIG10 is a schematic diagram of a subcomponent filling code template provided in an embodiment of the present application;

11 is a schematic diagram of a code adaptation template corresponding to a Vue framework provided in an embodiment of the present application;

12 is a schematic diagram of a code adaptation template corresponding to another Vue framework provided in an embodiment of the present application;

FIG13 is a schematic diagram of a code adaptation template corresponding to a React framework provided in an embodiment of the present application;

FIG14 is a schematic diagram of a code adaptation template corresponding to another React framework provided in an embodiment of the present application;

FIG15 is a schematic diagram of the structure of a computer device provided in an embodiment of the present application;

FIG16 is an architecture diagram of a computing device cluster provided in an embodiment of the present application;

FIG17 is a schematic diagram of a connection between computing devices provided in an embodiment of the present application;

FIG18 is a schematic diagram of the structure of a code generation device provided in an embodiment of the present application.

DETAILED DESCRIPTION

In order to make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

For ease of understanding, before explaining in detail the code generation method provided in the embodiment of the present application, the nouns and application scenarios involved in the embodiment of the present application are first introduced.

JavaScript ("JS" for short): is a programming language. It is a translated scripting language. It does not generate executable code directly. Instead, it passes the compiled code as bytecode to the compiler, which converts the bytecode into executable machine code to control the web page or application. JavaScript is usually used to write client-side scripts, that is, scripts that run in the browser. In addition to running in the browser, JavaScript can also be used to develop web applications.

Web application: is an application program accessed through Web technology. It can run in a Web browser and use a Web server to provide dynamic and interactive Web content. Users can easily access and use the application through a Web browser without installing other software or downloading installation packages.

User interface (UI) component library: A component library used to develop web applications and is part of the web application design system. The UI component library contains various UI components, such as buttons, labels, tables, input boxes, check boxes, drop-down boxes, date selection boxes, button tables, menus, breadcrumbs, trees, dialog boxes, sliders, switches, etc. In the process of web application design, UI components can be combined as needed to solve various design problems. The UI component library can facilitate designers and developers to share interface designs when developing web applications, improve work efficiency, and also enhance the brand sense and consistency of products. Therefore, the UI component library has the basic characteristics of versatility, flexibility, and reusability. Among them, versatility means that the components in the UI component library are basic and common enough without business attributes. Everyone involved in the design process should know the function and purpose of this component, and it has a certain degree of scalability. Flexibility means that the combination of components must be flexible. In different scenarios, they can be combined to quickly build interactive framework prototypes, and adapt to new business needs according to the evolution of different page structures. Reusability means that the components in the UI component library can be applied to multiple businesses or products, and can be reused frequently during the design process and R&D process.

React: React.js is a JavaScript-based framework. It is an open source web application development framework that aims to provide a simple, flexible, and scalable way to create web applications. React is widely used in web front-end development and has become one of the mainstream frameworks for building web applications.

Vue: The full name is Vue.js, which is a framework based on JavaScript. It is an open source web application development framework and a progressive JavaScript framework for building user interfaces. Vue is widely used in web front-end development and has become one of the mainstream frameworks for building web applications.

Lifecycle-oriented programming: is a programming paradigm. Under the Web application development framework, each component of a Web application has a life cycle of creation, mounting, updating, and destruction. Lifecycle-oriented programming is to enable each component of a Web application to execute correctly in different life cycle stages. In lifecycle-oriented programming, the creation, destruction, and management of objects are the focus of programming. Programmers need to consider how to correctly manage objects in different life cycle stages to ensure the correctness and stability of the program. In other words, lifecycle-oriented programming means that when developing a Web front-end UI component based on the Web application development framework, the relevant logic code of the UI component is registered in the specified life cycle hook function according to the life cycle defined by the Web application development framework. The life cycle hook function is a function triggered during the mounting and unmounting process of a component, which is used to perform some cleanup operations or event processing. The life cycle hook function is divided into the mounting phase, the updating phase, and the destruction phase according to the process of the component life cycle, and different operations are triggered according to different phases. Usually, when a component is unmounted, all life cycle hook functions are called once to ensure that the component is properly cleaned up. Taking the life cycle of the Vue framework as an example, the life cycle hook functions include: beforeCreate, created, beforeMount, mounted, beforeUnmount, unmounted, etc. The logic code of a UI component may be split into life cycle hook functions. Since life cycle-oriented programming is carried out in stages, errors in one stage will be carried over to the next stage, thereby expanding the scope of the error's impact, making the development process of Web applications relatively complex and slow.

Business logic-oriented programming: In the process of front-end development practice, especially when developing large-scale applications, a new programming paradigm is proposed to solve the problems caused by lifecycle-oriented programming. Business logic-oriented programming aims to describe and process business logic in a structured way. The main goal of business logic-oriented programming is to improve the readability, maintainability and extensibility of the code, making it easy to understand and modify. Among them, the API for business logic programming provided by the React framework is called Hooks API, and the API provided by the Vue framework is called Composition API. Other emerging front-end development frameworks that are emerging, such as Svelte and SolidJS frameworks, also provide similar APIs. Therefore, business logic-oriented programming is gradually replacing lifecycle-oriented programming and becoming the mainstream programming paradigm of Web front-end development frameworks.

Renderless Component: It is a design pattern for developing components. It separates the functional logic (business logic) of the component from the front-end rendering, making the component code more concise and easier to maintain. The core idea of renderless components is to write the logic code (business logic code) and rendering code (appearance code) of the component separately, so that the component code can be reused. This design pattern helps to improve the readability and maintainability of the code, making the component code more concise.

Next, the application scenarios of the embodiments of the present application are introduced.

In the process of Web application development, in order to improve the efficiency of code writing, technicians usually use JS-based development frameworks to design Web applications, such as Vue, React, and so on.

However, when designing a Web application, the Web application code written by the technician includes business logic code and appearance code, but because Web applications usually need to adapt to different terminal devices such as mobile phones, computers, and vehicle-mounted terminals, and the appearance of Web applications corresponding to different terminal devices is different. In other words, for the same Web application, the Web application has corresponding versions under different terminal devices, such as the version on the personal computer (PC), the version on the mobile phone, the version on the vehicle terminal, and so on. In addition, in order to ensure that the designed Web application is compatible with the mainstream development framework, for the same Web application, the technician also needs to design the Web application under different development frameworks. In other words, for a Web application, the Web application needs to have corresponding versions under different development frameworks, such as a version based on the Vue framework, a version based on the React framework, and so on.

Therefore, in order to ensure that the designed Web application is compatible with the mainstream development framework, it can also be adapted to different terminal devices. Under different development frameworks and different terminal devices, the same Web application has a PC version based on the Vue framework, a mobile phone version based on the Vue framework, a car terminal version based on the Vue framework, a PC version based on the React framework, a mobile phone version based on the React framework, a car terminal version based on the React framework, etc. In this way, for the same Web application, multiple versions need to be developed to adapt to different development frameworks and different terminal devices.

Since different technical knowledge is required for developing Web applications for different development frameworks and different terminal devices, different technicians are needed to develop and maintain different versions of Web applications. For example, technicians who understand the React framework are needed to develop and maintain the version based on the React framework, technicians who understand the Vue framework are needed to develop and maintain the version based on the Vue framework, technicians who understand PC-side interaction are needed to develop and maintain the PC-side version, technicians who understand mobile-side interaction are needed to develop and maintain the mobile-side version, and technicians who understand vehicle-mounted terminal interaction are needed to develop and maintain the vehicle-mounted terminal version. In this case, for Web applications with the same business logic, technicians need to repeatedly write the code for Web applications for different terminals and different development frameworks so that the Web applications are compatible with the mainstream development framework and have an appearance that is compatible with the terminal device. This will cause technicians to spend a lot of time writing code, which greatly increases labor costs and time costs.

Based on this, the embodiment of the present application provides a code generation method, which can obtain the business logic code of the target application and at least one appearance code of the target application under the target development framework, so as to determine the complete code of the target application under the target development framework based on the business logic code and the at least one appearance code. Since the at least one appearance code indicates at least one appearance of the target application, and the at least one appearance corresponds to at least one terminal type, the complete code can ensure that the target application is compatible with the target development framework while also ensuring that the appearance of the target application can adapt to different terminal devices. In other words, the code generation method provided by the embodiment of the present application can automatically generate the complete code of the target application under the target framework, without the need for technicians to repeatedly write the code for the target application for different terminals and different development frameworks, thereby greatly improving the efficiency of code writing and effectively saving manpower and time costs.

The execution subject of the code generation method provided in the embodiment of the present application is a cloud platform, that is, the cloud platform can provide code generation services. The cloud platform can be a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms, or a cloud computing service center.

It should be noted that the application scenarios and execution entities described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the emergence of new application scenarios and the evolution of equipment, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

Fig. 1 is a flow chart of a code generation method provided by an embodiment of the present application. Referring to Fig. 1 , the method comprises the following steps.

Step 101: Obtain a business logic code of a target application and at least one appearance code of the target application in a target development framework, wherein the business logic code indicates a function of the target application, and the at least one appearance code indicates at least one appearance of the target application, and the at least one appearance corresponds to at least one terminal type.

There are multiple implementation methods for obtaining the business logic code of the target application and at least one appearance code of the target application under the target development framework, and two of them are introduced below.

In the first implementation method, the cloud platform can display a code writing interface, which is used to write the business logic code of the target application and at least one appearance code of the target application under the target development framework. In response to the code writing completion operation, the cloud platform can obtain the business logic code of the target application and at least one appearance code of the target application under the target development framework.

After the cloud platform displays the code writing interface, the technician can write the business logic code and the at least one appearance code of the target application in the code writing interface. After the writing is completed, the technician triggers the code writing completion operation, and the cloud platform responds to the code writing completion operation to obtain the business logic code of the target application and the at least one appearance code of the target application under the target development framework.

For example, the technician first writes the business logic code of the target application in the code writing interface, and after the business logic code is written, the business logic code writing completion operation is triggered. In response to the business logic code writing completion operation, the cloud platform obtains the business logic code and resets the code writing interface to facilitate the technician to continue writing the appearance code of the target application under the target development framework. Furthermore, the technician writes at least one appearance code in the code writing interface, and after the at least one appearance code is written, the at least one appearance code writing completion operation is triggered, and the cloud platform obtains the at least one appearance code in response to the at least one appearance code writing completion operation.

Since the technician can write at least one appearance code, in this case, every time the technician finishes writing an appearance code, the operation of writing the next appearance code can be triggered, and the operation of completing the writing of at least one appearance code can also be triggered. If the technician triggers the operation of writing the next appearance code, the cloud platform responds to the operation of writing the next appearance code, saves the appearance code in the current code writing interface, and resets the code writing interface so that the technician can continue to write the next appearance code. If the technician triggers the operation of completing the writing of at least one appearance code, the cloud platform responds to the operation of completing the writing of the at least one appearance code, and uses the appearance code in the current code writing interface and the previously saved appearance code as the at least one appearance code.

If the technician triggers the operation of writing the next appearance code, it means that the technician still needs to write an appearance code. Therefore, the cloud platform can respond to the operation of the next appearance code, save the appearance code in the current code writing interface, and reset the code writing interface to facilitate the technician to continue writing the next appearance code. If the technician triggers the operation of completing the writing of at least one appearance code, it means that the technician has finished writing all the appearance codes. Therefore, the cloud platform can respond to the operation of completing the writing of at least one appearance code and use the appearance code in the current code writing interface and the previously saved appearance code as the at least one appearance code.

For example, the cloud platform can display the code writing interface shown in Figure 2. After the technician finishes writing the business logic code of the target application, the operation of completing the writing of the business logic code can be triggered. Then, the technician can continue to write at least one appearance code in the code writing interface. After the technician finishes writing an appearance code, the operation of writing the next appearance code can be triggered in the interface shown in Figure 3, and the operation of completing the writing of at least one appearance code can also be triggered.

It should be noted that the above process of first writing the business logic code and then writing the appearance code in the code writing interface is only an example. In actual applications, you can also first write at least one appearance code and then write the business logic code of the target application. The embodiments of the present application are not limited to this.

In the second implementation method, the technicians can complete the writing of the business logic code and the at least one appearance code of the target application on other cloud platforms with code writing functions, and then send the business logic code and the at least one appearance code of the target application to the cloud platform, and the cloud platform receives the business logic code and the at least one appearance code of the target application.

That is to say, the business logic code and the at least one appearance code of the target application can be directly obtained by the technician after writing on the cloud platform, or can be sent to the cloud platform after the technician writes on other cloud platforms with code writing functions. Of course, in actual applications, the cloud platform can also obtain the business logic code and the at least one appearance code of the target application in other ways, which is not limited in the embodiments of the present application.

In some embodiments, the business logic code is in the form of a curried function, and the business logic code and the at least one appearance code are in JavaScript language.

As an example, when the target application is a to-do (TODO) component, the business logic code of the to-do component may be the code shown below, and the business logic code indicates that the to-do component has the functions of deleting to-do items and adding to-do items.

Step 102: Based on the business logic code, determine the rendering-free code of the target application under the target development framework.

In some embodiments, the rendering-free code of the target application under the target development framework may be determined according to the following steps (1)-(2).

(1) Determine the function name of at least one logic function in the business logic code, the parameter name of at least one parameter corresponding to the at least one logic function, and the attribute name of each parameter in the at least one parameter.

In some embodiments, the business logic code includes logic code comments and a logic code body. In this case, the function name of the at least one logic function can be obtained from the logic code body, and the parameter name of at least one parameter corresponding to the at least one logic function and the attribute name of each parameter can be obtained from the logic code comments.

The cloud platform can determine a first position from the business logic code body, where the code at the first position contains the function name of the at least one logic function, and obtain the function name of the at least one logic function from the code at the first position.

For example, the cloud platform stores a first string. In this case, the cloud platform can search for the first string from the business logic code according to the relevant algorithm, determine the location of the first string as the first position, and use the code at the first position except the first string as the function name of at least one logical function.

For example, taking the above-mentioned business logic code as an example, the first string can be export{}, the cloud platform determines the location of the first string as the first position, and the code at the first position is export{addTag, removeTag}. Then, the code at the first position except the first string is addTag and removeTag, so addTag and removeTag can be used as the function name of at least one logical function.

It should be noted that the above-mentioned first string is stored in the cloud platform in advance is only an example. In actual applications, the first string can also be determined by other means, and the embodiments of the present application do not limit this. For example, the technician can also enter the first string in the cloud platform so that the cloud platform can obtain the first string. In the case where the technician enters the first string, the cloud platform can display the first string input interface, and in response to the first string input completion operation, obtain the first string entered by the technician. For example, the cloud platform can display the first string designation interface as shown in Figure 4, and the technician can enter the first string in the first string designation interface. After the input is completed, the technician can trigger the first string input completion operation. The cloud platform responds to the first string input completion operation triggered by the technician and obtains the first string entered by the technician.

Based on the above description, the function name of the at least one logic function can be determined by the cloud platform itself from the business logic code body. In practical applications, the function name of the at least one logic function can also be determined by other means. For example, a technician can directly enter the function name of the at least one logic function in the cloud platform so that the cloud platform can obtain the function name of the at least one logic function. This embodiment of the present application is not limited to this. The implementation process of the technician entering the function name of at least one logic function in the cloud platform is similar to the implementation process of the above-mentioned technician entering the first string in the cloud platform. For the detailed implementation process, please refer to the relevant content above, which will not be repeated here.

In order to facilitate the cloud platform to identify the logic code annotation, in some embodiments, the format of the logic code annotation is a target format. In this case, the cloud platform stores the target format in advance, and the cloud platform can determine the parameter name of at least one parameter and the attribute name of at least one parameter corresponding to at least one logic function from the logic code annotation according to the target format and the relevant algorithm.

In some embodiments, the target format is a jsdoc format. Of course, the format of the logic code comment can also be other types of formats, which is not limited in the embodiments of the present application. For example, when the target format is a jsdoc format, each logic function in at least one logic function corresponds to a logic code sub-comment. The cloud platform can determine the parameter name of at least one parameter corresponding to each logic function and the attribute name of each parameter from the logic code sub-comment corresponding to each logic function according to the relevant algorithm.

Continuing with the above business logic code as an example, the business logic code includes two logic functions, addTag and removeTag. The logic code sub-comment corresponding to addTag is shown below.

/**

*@param{object}text-the data type of the parameter named text is object

*@param{boolean}text.model - The parameter text includes an attribute named model, and the data type of the model attribute is boolean

*@param{string}text.value-The parameter text includes an attribute with the attribute name value, and the data type of the value attribute is string, that is, the data type of the value of the parameter text is string.

*@param{object}props-The data type of the parameter named props is object

*@param{object}refs-The data type of the parameter named refs is object

*@param{function}emit-The data type of the parameter named emit is function

*@param{object}api-the data type of the parameter named api is object

*/

In the logic code sub-annotation corresponding to addTag, the cloud platform can determine that the parameter name of at least one parameter corresponding to addTag is text, props, refs, emit, and api, where the attribute name of the parameter text includes model and value, and other parameters have no attributes.

The logic code sub-comments corresponding to removeTag are shown below.

/**

*@param{object}props-The data type of the parameter named props is object

*@param{object}refs-The data type of the parameter named refs is object

*@param{function}emit-The data type of the parameter named emit is function

*/

In the logic code sub-comment corresponding to removeTag, the cloud platform can determine that the parameter names of at least one parameter corresponding to removeTag are props, refs, and emit, and these parameters have no attributes.

(2) Based on the function name of the at least one logic function, the parameter name of the at least one parameter, the attribute name of each parameter in the at least one parameter, and the storage path of the business logic code, the rendering-free template corresponding to the target development framework is filled to obtain the rendering-free code of the target application under the target development framework.

In some embodiments, the non-rendering template corresponding to the target development framework includes a first area to be filled, and the first area to be filled includes a logic function import sub-area, a logic code path sub-area, an initialization sub-area, an API object creation area, a mount and update area, and an API object created area. In this case, the function name of the at least one logic function can be written into the logic function import sub-area, the storage path of the business logic code can be written into the logic code path sub-area, the parameter with the target attribute name in at least one parameter is used as the first parameter, and the target attribute name indicates that the parameter with the target attribute name is a data model, and the initialization sub-area is filled based on the first parameter, and the parameter name of the first parameter and the function name of the first logic function in at least one logic function are written into the API object creation area, and the first logic function is a logic function without a target parameter name, and the target parameter name indicates that the logic function with the target parameter name is an interface function. If there is a mount function in at least one logic function, the code of the function name of the mount function under the target framework is written into the mount and update area. The function names of the logic functions other than the first logic function in at least one logic function are written into the API object created area to achieve the filling of the non-rendering template corresponding to the target development framework.

The implementation process of filling the initialization sub-area based on the first parameter includes: determining the initialization code of the first parameter in the target framework, and writing the initialization code into the initialization sub-area.

The cloud platform stores the correspondence between the target attribute name and the initialization code under the target framework. Based on the attribute name included in the first parameter that is the same as the target attribute name, the initialization code of the first parameter under the target framework can be determined from the correspondence between the target attribute name and the initialization code under the target framework.

It should be noted that the above target attribute name, target parameter name and function name of the mounting function are set in advance. The target attribute name can be set to model, the target parameter name can be set to api, and the function name of the mounting function can be set to mounted. Of course, in actual applications, the target attribute name, target parameter name and function name of the mounting function can also be set to other names, which is not limited in the embodiments of the present application.

As an example, the non-rendering template corresponding to the Vue framework is shown in Figure 5. Please refer to Figure 6. If the function name of at least one logic function is addTag, removeTag, checkTag, focus, inputEvents, mounted, the function name of the at least one logic function can be written into the logic function import sub-area, and the storage path of the business logic code can be written into the logic code path sub-area. If the attribute name of the parameter text of addTag includes model and value, the parameter text is a parameter with the target attribute name (model). Therefore, the parameter text of addTag can be used as the first parameter, and the first parameter can be initialized in the Vue framework. “parent.text＝parent.text||value(”)” is written into the initialization sub-area. If checkTag, focus and removeTag are the first logical functions, text, checkTag, focus and removeTag are written into the API object creation area. Because there is a mounting function in at least one logical function, the function name of the mounting function can be written into the mounting and update area in the code “onMounted(mounted(api))onUpdated(mounted(api))” under the Vue framework. AddTag and inputEvents are written into the API object created area.

As another example, the non-rendering template corresponding to the React framework is shown in FIG7 . Please refer to FIG8 . If the function name of at least one logic function is addTag, removeTag, checkTag, focus, inputEvents, mounted, the function name of the at least one logic function can be written into the logic function import sub-area, and the storage path of the business logic code can be written into the logic code path sub-area. If the attribute name of the parameter text of addTag includes model and value, the parameter text is a parameter with the target attribute name (model). Therefore, the parameter text of addTag can be used as the first parameter, and the initialization code of the first parameter in the React framework "const text＝value(")" is written into the initialization sub-area. If checkTag, focus, and removeTag are the first logic functions, text, checkTag, focus, and removeTag are written into the API object creation area. Because the function name of the mounting function exists in the function name of at least one logic function, the function name of the mounting function can be written into the code "onMounted(mounted(api))onUpdated(mounted(api), [context.$mo de])" to the mount and update area. Write addTag and inputEvents to the API object created area.

In actual applications, before filling the non-rendering template corresponding to the target development framework, the cloud platform needs to determine the target development framework. In this case, the cloud platform can display a development framework selection interface as shown in Figure 9, which is used to select the target development framework. In response to the development framework selection completion operation, the cloud platform can determine the target development framework. That is, after the cloud platform displays the development framework selection interface, the technician can select a development framework as the target development framework in the development framework selection interface. After the selection is completed, the technician can trigger the development framework selection completion operation. The cloud platform determines the target development framework in response to the development framework selection completion operation.

Step 103: Organize the non-rendering code and at least one appearance code to obtain the complete code of the target application under the target development framework.

Since there are multiple development frameworks, different development frameworks have different ways of obtaining the complete code of the target application under the target development framework. Next, the corresponding implementation methods of two of the development frameworks are introduced.

In the first case, the target development framework is the Vue framework, the target application is a Web application, the target application includes at least one component, and the at least one appearance code indicates at least one appearance of the at least one component. In this case, based on the at least one appearance code, the component name of the subcomponent contained in the at least one component and the attribute name of the at least one component can be determined, and based on the attribute name of the at least one component, the component name of the subcomponent and the storage path of the non-rendering code, the code adaptation template corresponding to the target development framework is filled to obtain the complete code of the target application under the target development framework.

Each appearance code in the at least one appearance code includes an appearance code comment. In this case, the component name of the subcomponent in the at least one component and the attribute name of the at least one component can be obtained from the appearance code comment.

In order to facilitate the cloud platform to identify the appearance code annotation, in some embodiments, the format of the appearance code annotation is a target format. In this case, the cloud platform stores the target format in advance, and the cloud platform can determine the component name of the subcomponent in the at least one component and the attribute name of the at least one component from the appearance code annotation according to the target format and the relevant algorithm.

In some embodiments, the target format is jsdoc format. Of course, the format of the logic code annotation can also be other types of formats, which are not limited in the embodiments of the present application.

For example, when the target format is jsdoc format, each appearance code in at least one appearance code corresponds to an appearance code comment. The cloud platform can obtain the component name of the subcomponent in at least one component and the attribute name of the at least one component from the appearance code comment corresponding to each appearance code according to a relevant algorithm.

As an example, the appearance code annotation is shown below.

/**

*@property{array}tags-at least one component's property name includes tags, and the data type of the tags property is array.

*@property{string}newTag-at least one component's property name includes newTag, and the data type of the tags property is string

*@module TodoTag - Each component contains subcomponents whose component names include TodoTag

*/

In the above appearance code annotation, the cloud platform may determine that the attribute name of at least one component includes tags and newTag, and the component name of the subcomponent in at least one component includes TodoTag.

In some embodiments, the code adaptation template corresponding to the target development framework includes a second area to be filled, and the second area to be filled includes a non-rendering code path sub-area, a component attribute sub-area, and a sub-component sub-area. In this case, based on the attribute name of at least one component, the component name of the sub-component contained in at least one component, and the storage path of the non-rendering code, the implementation process of filling the code adaptation template corresponding to the target development framework includes: writing the storage path of the non-rendering code into the non-rendering code path sub-area, writing the attribute name of at least one component into the component attribute sub-area, and filling the sub-component sub-area based on the component name of the sub-component contained in at least one component.

In some embodiments, a subcomponent filling code template is stored in the cloud platform, and the subcomponent filling code template includes a name area and a path area. In this case, based on the component name of the subcomponent contained in at least one component, the implementation process of filling the subcomponent subarea includes: for any subcomponent contained in at least one component, the component name of the subcomponent is written into the name area of the subcomponent filling code template, and the storage path of the complete code of the subcomponent is written into the path area of the subcomponent filling code template to obtain the filling code corresponding to the subcomponent. For each subcomponent contained in at least one component, the filling code corresponding to each subcomponent can be obtained in the same manner, and the filling code corresponding to each subcomponent is written into the subcomponent subarea to achieve the filling of the subcomponent subarea.

As an example, please refer to FIG. 10 , the subcomponent filling code template may be the template shown in FIG. 10 , which includes a name area and a path area.

In order to facilitate technical personnel to improve the development efficiency and code quality of applications, the target development framework also has corresponding tool library codes. In this case, the code adaptation template corresponding to the target development framework also includes a tool library path sub-area, and the cloud platform can write the storage path of the tool library code corresponding to the target development framework into the tool library path sub-area.

As an example, the code adaptation template corresponding to the Vue framework is shown in Figure 11. Please refer to Figure 12. If the storage path of the non-rendering code is "../../renderless/Todo/vue", the storage path of the non-rendering code can be written into the non-rendering code path sub-area. If the storage path of the tool library code corresponding to the target development framework is "../common", the storage path of the tool library code can be written into the tool library path sub-area. If the attribute names of at least one component are newTag and tags, newTag and tags can be written into the component attribute sub-area. If the fill code corresponding to each sub-component is "TodoTag:()＝>import('../Tag')", the fill code can be written into the sub-component sub-area.

In the second case, the target development framework is the React framework, the target application is a Web application, the target application includes at least one component, and the at least one appearance code indicates at least one appearance of the at least one component. In this case, the attribute name of the at least one component can be determined based on the at least one appearance code, the function name of at least one logic function in the business logic code can be determined, and the code adaptation template corresponding to the target development framework can be filled based on the attribute name of the at least one component, the function name of the at least one logic function, and the storage path of the non-rendering code, so as to obtain the complete code of the target application under the target development framework.

In some embodiments, each of the at least one appearance code includes an appearance code body, or includes an appearance code body and an appearance code comment. In the case where the appearance code includes the appearance code body, the attribute name of at least one component is obtained from the appearance code body; in the case where the appearance code includes the appearance code body and the appearance code comment, the attribute name of at least one component is obtained from the appearance code body or the appearance code comment.

The cloud platform may determine a second position from the appearance code body, where the code at the second position includes the attribute name of the at least one component, and obtain the attribute name of the at least one component from the code at the first position.

For example, the cloud platform stores a second string. In this case, the cloud platform can search for the second string from the appearance code body according to the relevant algorithm, determine the location of the second string as the second location, and use the code at the second location except the second string as the attribute name of at least one component.

For example, if the second string is const{}＝props, the cloud platform determines the location of the second string as the second position. If the code at the second position is const{addTag,removeTag,value,keydown,input,tags,ref,$mode}＝props, then the code at the second position except the second string is addTag, removeTag, value, keydown, input, tags, ref and $mode. Therefore, addTag, removeTag, value, keydown, input, tags, ref and $mode can be used as the attribute name of at least one component.

It should be noted that the above-mentioned second string is stored in the cloud platform in advance is only an example. In actual applications, the second string can also be determined by other means, and the embodiments of the present application do not limit this. For example, the technician can also enter the second string in the cloud platform so that the cloud platform can obtain the second string. In the case where the technician enters the second string, the cloud platform can display the second string input interface, and in response to the second string input completion operation, obtain the second string entered by the technician. For example, the cloud platform can display the second string designation interface, and the technician can enter the second string in the second string designation interface. After the input is completed, the technician can trigger the second string input completion operation. The cloud platform responds to the second string input completion operation triggered by the technician and obtains the second string entered by the technician.

Based on the above description, the attribute name of the at least one component can be determined by the cloud platform from the appearance code body. In practical applications, the attribute name of the at least one component can also be determined by other means. For example, a technician can directly enter the attribute name of the at least one component in the cloud platform so that the cloud platform can obtain the attribute name of the at least one component. This embodiment of the present application is not limited to this. The implementation process of the technician entering the attribute name of at least one component in the cloud platform is similar to the implementation process of the above-mentioned technician entering the first string in the cloud platform. For the detailed implementation process, please refer to the relevant content above, which will not be repeated here.

The implementation method of determining the attribute name of at least one component from the appearance code is similar to the implementation method of determining the attribute name of at least one component from the appearance code comment in the first implementation method mentioned above. Please refer to the relevant content above for the detailed implementation process, which will not be repeated here.

In some embodiments, the code adaptation template corresponding to the React development framework includes a third area to be filled, and the third area to be filled includes a non-rendering code path sub-area, a component attribute sub-area, and a logic function sub-area. In this case, based on the attribute name of the at least one component, the function name of the at least one logic function, and the storage path of the non-rendering code, the implementation process of filling the code adaptation template corresponding to the target development framework includes: writing the storage path of the non-rendering code into the non-rendering code path sub-area, writing the attribute name of at least one component into the component attribute sub-area, and writing the function name of at least one logic function into the logic function sub-area.

In order to facilitate technical personnel to improve the development efficiency and code quality of applications, the target development framework also has corresponding tool library codes. In this case, the code adaptation template corresponding to the target development framework also includes a tool library path sub-area, and the cloud platform can write the storage path of the tool library code corresponding to the target development framework into the tool library path sub-area.

As an example, the code adaptation template corresponding to the React framework is shown in Figure 13. Please refer to Figure 14. If the storage path of the non-rendering code is "../../renderless/Todo/react", the storage path of the non-rendering code can be written into the non-rendering code path sub-area. If the storage path of the tool library code corresponding to the target development framework is "../common/index", the storage path of the tool library code can be written into the tool library path sub-area. If the attribute name of at least one component is addTag, removeTag, value, keydown, input, tags, ref and $mode, newTag and tags can be written into the component attribute sub-area. If the function name of at least one logic function is addTag, removeTag, inputEvents and text, the function name of the at least one logic function can be written into the logic function sub-area.

The embodiment of the present application obtains the business logic code of the target application and at least one appearance code of the target application under the target development framework, thereby determining the complete code of the target application under the target development framework based on the business logic code and the at least one appearance code. Since the at least one appearance code indicates at least one appearance of the target application, and the at least one appearance corresponds to at least one terminal type, the complete code can ensure that the target application is compatible with the target development framework while also ensuring that the appearance of the target application can adapt to different terminal devices. In other words, a code generation method provided in the embodiment of the present application can automatically generate the complete code of the target application under the target framework, without the need for technical personnel to repeatedly write the code for the target application for different terminals and different development frameworks, thereby greatly improving the efficiency of code writing and effectively saving manpower and time costs.

The embodiment of the present application also provides a computing device 100. As shown in FIG. 15 , the computing device 100 includes: a bus 102, a processor 104, a memory 106, and a communication interface 108. The processor 104, the memory 106, and the communication interface 108 communicate with each other through the bus 102. The computing device 100 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the computing device 100.

The bus 102 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, FIG. 15 is represented by only one line, but does not mean that there is only one bus or one type of bus. The bus 102 may include a path for transmitting information between various components of the computing device 100 (e.g., the memory 106, the processor 104, and the communication interface 108).

The processor 104 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), a digital signal processor (DSP), an integrated circuit, etc. The integrated circuit may be an ASIC, a PLD, or a combination thereof. Optionally, the PLD may be a CPLD, an FPGA, a GAL, or any combination thereof.

The memory 106 may include a volatile memory, such as a random access memory (RAM). The memory 106 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid state drive (SSD), or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 106 exists independently and is connected to the processor 104 through the bus 102, or the memory 106 is integrated with the processor 104.

The memory 106 stores executable program codes, and the processor 104 executes the executable program codes to implement the aforementioned code generation method. That is, the memory 106 stores instructions for executing the code generation method.

For example, the memory 106 stores executable code, and the processor 104 executes the executable code to implement the functions of the acquisition module, the determination module, and the organization module as shown in Figure 18 below. That is, the memory 106 stores instructions for executing the code generation method provided in the embodiment of the present application.

The communication interface 108 uses a transceiver module such as, but not limited to, a network interface card and a transceiver to implement communication between the computing device 100 and other devices or communication networks. The network interface includes a wired communication interface, or also includes a wireless communication interface. Among them, the wired communication interface is, for example, an Ethernet interface. The Ethernet interface is an optical interface, an electrical interface, or a combination thereof. The wireless communication interface is a wireless local area network (WLAN) interface, a cellular network communication interface, or a combination thereof.

The embodiment of the present application also provides a computing device cluster. The computing device cluster includes multiple computing devices. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

As shown in Fig. 16, the computing device cluster includes multiple computing devices 100. The same instructions for executing the above code generation method may be stored in the memory 106 of the multiple computing devices 100 in the computing device cluster.

In some possible implementations, the memory 106 of the multiple computing devices 100 in the computing device cluster may also store partial instructions for executing the above code generation method. In other words, the combination of the multiple computing devices 100 can jointly execute all instructions for executing the above code generation method.

It should be noted that the memory 106 in different computing devices 100 in the computing device cluster may store different instructions for executing part of the functions of the above-mentioned code generation method. That is, the instructions stored in the memory 106 in different computing devices 100 may implement the functions of some or all modules included in the code generation apparatus described below.

In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network. The network may be a wide area network or a local area network, etc. FIG. 17 shows a possible implementation. As shown in FIG. 17 , two computing devices 100A and 100B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 106 in the computing device 100A stores instructions for executing the functions of a portion of the modules included in the code generation device hereinafter. At the same time, the memory 106 in the computing device 100B stores instructions for executing the functions of another portion of the modules included in the code generation device hereinafter.

For example, the memory 106 in the computing device 100A stores instructions for executing the functions of the acquisition module and the determination module included in the code generation apparatus described below. Meanwhile, the memory 106 in the computing device 100B stores instructions for the functions of the organization module.

It should be understood that the functions of the computing device 100A shown in FIG17 may also be completed by multiple computing devices 100. Similarly, the functions of the computing device 100B may also be completed by multiple computing devices 100.

The embodiment of the present application also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to the connection mode of the computing device cluster described in Figures 16 and 17. The difference is that the memory 106 in one or more computing devices 100 in the computing device cluster can store the same instructions for executing the code generation method.

In some possible implementations, the memory 106 of one or more computing devices 100 in the computing device cluster may also store partial instructions for executing the code generation method. In other words, the combination of one or more computing devices 100 may jointly execute instructions for executing the code generation method.

FIG18 is a schematic diagram of the structure of a code generation device provided in an embodiment of the present application, and the code generation device can be implemented as part or all of the cloud platform by software, hardware or a combination of both. Referring to FIG18 , the device includes: an acquisition module 1801 , a determination module 1802 and an organization module 1803 .

The acquisition module 1801 is used to acquire the business logic code of the target application and at least one appearance code of the target application under the target development framework, wherein the business logic code indicates the function of the target application, and the at least one appearance code indicates at least one appearance of the target application, and the at least one appearance corresponds to at least one terminal type. The detailed implementation process refers to the corresponding content in the above-mentioned embodiments, which will not be repeated here.

The determination module 1802 is used to determine the non-rendering code of the target application under the target development framework based on the business logic code. The detailed implementation process refers to the corresponding content in the above embodiments, which will not be repeated here.

The organization module 1803 is used to organize the non-rendering code and at least one appearance code to obtain the complete code of the target application under the target development framework. The detailed implementation process refers to the corresponding content in the above embodiments, which will not be repeated here.

Optionally, the determination module 1802 is specifically configured to:

Determine a function name of at least one logic function in the business logic code, a parameter name of at least one parameter corresponding to the at least one logic function, and an attribute name of each parameter in the at least one parameter;

Based on the function name of at least one logical function, the parameter name of at least one parameter, the attribute name of each parameter and the storage path of the business logic code, the renderingless template corresponding to the target development framework is filled to obtain the renderingless code of the target application under the target development framework.

Optionally, the business logic code includes logic code comments and logic code body;

The determination module 1802 is specifically used for:

Obtaining a function name of at least one logic function from the logic code body;

The parameter name of at least one parameter corresponding to at least one logic function and the attribute name of each parameter are obtained from the logic code annotation.

Optionally, the target application is a Web application, the target development framework is a Vue framework, the target application includes at least one component, and the at least one appearance code indicates at least one appearance of the at least one component;

The organization module 1803 is specifically used for:

Determine, based on at least one appearance code, a component name of a subcomponent included in the at least one component and an attribute name of at least one component;

Based on the attribute name of at least one component, the component name of the subcomponent and the storage path of the non-rendering code, the code adaptation template corresponding to the target development framework is filled to obtain the complete code of the target application under the target development framework.

Optionally, each appearance code in the at least one appearance code includes an appearance code annotation;

The organization module 1803 is specifically used for:

Get the component name of the child component and at least one component property name from the appearance code comment.

Optionally, the target application is a Web application, the target development framework is a React framework, the target application includes at least one component, and the at least one appearance code indicates at least one appearance of the at least one component;

The organization module 1803 is specifically used for:

determining a property name of at least one component based on at least one appearance code;

Determine a function name of at least one logic function in the business logic code;

Based on the property name of at least one component, the function name of at least one logic function, and the storage path of the non-rendering code, the code adaptation template corresponding to the target development framework is filled to obtain the complete code of the target application under the target development framework.

Optionally, each appearance code in the at least one appearance code includes an appearance code body, or includes an appearance code body and an appearance code annotation;

The organization module 1803 is specifically used for:

In the case where the appearance code includes an appearance code body, obtaining an attribute name of at least one component from the appearance code body;

In the case that the appearance code includes an appearance code body and an appearance code comment, the attribute name of at least one component is obtained from the appearance code body or the appearance code comment.

Optionally, the business logic code is in the form of a curried function, and the business logic code and at least one appearance code are in JavaScript language.

The embodiment of the present application obtains the business logic code of the target application and at least one appearance code of the target application under the target development framework, thereby determining the complete code of the target application under the target development framework based on the business logic code and the at least one appearance code. Since the at least one appearance code indicates at least one appearance of the target application, and the at least one appearance corresponds to at least one terminal type, the complete code can ensure that the target application is compatible with the target development framework while also ensuring that the appearance of the target application can adapt to different terminal devices. In other words, a code generation method provided in the embodiment of the present application can automatically generate the complete code of the target application under the target framework, without the need for technical personnel to repeatedly write the code for the target application for different terminals and different development frameworks, thereby greatly improving the efficiency of code writing and effectively saving manpower and time costs.

It should be noted that: the code generation device provided in the above embodiment only uses the division of the above functional modules as an example when performing code generation. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the code generation device provided in the above embodiment and the code generation method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

The acquisition module, determination module and organization module in the code generation device shown in FIG18 can all be implemented by software, or can be implemented by hardware, or can be implemented by a combination of software and hardware. Next, taking the acquisition module in the code generation device as an example, the implementation method of the acquisition module is introduced. Similarly, the implementation methods of the above-mentioned other modules can refer to the implementation method of the acquisition module.

As an example of a software functional unit, a module may include code running on a computing instance. The computing instance may include at least one of a physical host, a virtual machine, and a container. Furthermore, the computing instance may be one or more. For example, the acquisition module may include code running on multiple hosts/virtual machines/containers. It should be noted that the multiple hosts/virtual machines/containers used to run the code may be distributed in the same region or in different regions. Furthermore, the multiple hosts/virtual machines/containers used to run the code may be distributed in the same AZ or in different AZs, and each AZ includes a data center or multiple data centers with close geographical locations. Generally, a region may include multiple AZs.

Similarly, multiple hosts/virtual machines/containers used to run the code can be distributed in the same VPC or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

As an example of a hardware functional unit, the acquisition module may include at least one computing device, such as a server, etc. Alternatively, the acquisition module may also be a device implemented by ASIC or PLD, etc. The PLD may be implemented by CPLD, FPGA, GAL or any combination thereof.

The multiple computing devices included in the acquisition module can be distributed in the same region or in different regions. The multiple computing devices included in the acquisition module can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the acquisition module can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

In other embodiments, the acquisition module in the code generating device can be used to execute any step in the above-mentioned code generating method, the receiving module in the code generating device can be used to execute any step in the above-mentioned code generating method, and the organization module in the code generating device can be used to execute any step in the above-mentioned code generating method. The steps that the acquisition module, receiving module and organization module in the code generating device are responsible for implementing can be specified as needed. The different steps in the above-mentioned code generating method are respectively implemented by the acquisition module, receiving module and organization module in the code generating device, thereby realizing all the functions of the code generating device.

The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct a computing device in a computer device cluster to execute the code generation method provided in the embodiment of the present application.

The embodiment of the present application also provides a computer program product including instructions. The computer program product may be a software or program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on a computing device included in a computing device cluster, the computing device cluster executes the code generation method provided in the embodiment of the present application.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access, or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital versatile disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)). It is worth noting that the computer-readable storage medium mentioned in the embodiment of the present application may be a non-volatile storage medium, in other words, a non-transient storage medium.

It should be understood that the "multiple" mentioned herein refers to two or more. In the description of the embodiments of the present application, unless otherwise specified, "/" means or, for example, A/B can mean A or B; "and/or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in order to facilitate the clear description of the technical solution of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish between the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not limit them to be necessarily different.

It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data for analysis, stored data, displayed data, etc.) and signals involved in the embodiments of the present application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions. For example, the business logic code of the target application involved in the embodiments of the present application and at least one appearance code of the target application under the target development framework are obtained with full authorization.

The above-mentioned embodiments are provided for the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims (19)

1. A code generation method, the method comprising:

acquiring a business logic code of a target application and at least one appearance code of the target application under a target development framework, wherein the business logic code indicates a function of the target application, the at least one appearance code indicates at least one appearance of the target application, and the at least one appearance corresponds to at least one terminal type;

determining rendering-free codes of the target application under the target development framework based on the business logic codes;

and organizing the rendering-free code and the at least one appearance code to obtain complete code of the target application under the target development framework.

2. The method of claim 1, wherein the determining, based on the business logic code, no rendering code for the target application under the target development framework comprises:

Determining a function name of at least one logic function in the service logic code, a parameter name of at least one parameter corresponding to the at least one logic function respectively and an attribute name of each parameter in the at least one parameter;

and filling the non-rendering template corresponding to the target development framework based on the function name of the at least one logic function, the parameter name of the at least one parameter, the attribute name of each parameter and the storage path of the business logic code, so as to obtain the non-rendering code of the target application under the target development framework.

3. The method of claim 2, wherein the business logic code comprises a logic code annotation and a logic code ontology; the determining the function name of at least one logic function in the service logic code, the parameter name of at least one parameter corresponding to the at least one logic function, and the attribute name of each parameter in the at least one parameter respectively includes:

acquiring the function name of the at least one logic function from the logic code body;

and acquiring the parameter name of at least one parameter and the attribute name of each parameter corresponding to the at least one logic function from the logic code annotation.

4. A method according to any of claims 1-3, wherein the target application is a Web application, the target development framework is a Vue framework, the target application comprises at least one component, and the at least one appearance code indicates at least one appearance of the at least one component; the organizing the non-rendered code and the at least one appearance code to obtain a complete code of the target application under the target development framework includes:

determining a component name of a sub-component contained in the at least one component and an attribute name of the at least one component based on the at least one appearance code;

and filling a code adaptation template corresponding to the target development framework based on the attribute name of the at least one component, the component name of the sub-component and the storage path of the rendering-free code, so as to obtain the complete code of the target application under the target development framework.

5. The method of claim 4, wherein each of the at least one appearance code comprises an appearance code annotation; the determining, based on the at least one appearance code, a component name of a sub-component in the at least one component and an attribute name of the at least one component, includes:

And acquiring the component name of the sub-component and the attribute name of the at least one component from the appearance code annotation.

6. A method according to any of claims 1-3, wherein the target application is a Web application, the target development framework is a act framework, the target application comprises at least one component, and the at least one appearance code indicates at least one appearance of the at least one component; the organizing the non-rendered code and the at least one appearance code to obtain a complete code of the target application under the target development framework includes:

determining an attribute name of the at least one component based on the at least one appearance code;

determining the function name of at least one logic function in the service logic code;

and filling a code adaptation template corresponding to the target development framework based on the attribute name of the at least one component, the function name of the at least one logic function and the storage path of the rendering-free code so as to obtain the complete code of the target application under the target development framework.

7. The method of claim 6, wherein each of the at least one appearance code comprises an appearance code body or comprises the appearance code body and an appearance code annotation; the determining the attribute name of the at least one component based on the at least one appearance code includes:

Acquiring an attribute name of the at least one component from the appearance code body when the appearance code includes the appearance code body;

and acquiring the attribute name of the at least one component from the appearance code body or the appearance code annotation when the appearance code comprises the appearance code body and the appearance code annotation.

8. The method of any of claims 1-7, wherein the business logic code is in the form of a cori function, and the business logic code and the at least one appearance code are in JavaScript language.

9. A code generating apparatus, the apparatus comprising:

the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a business logic code of a target application and at least one appearance code of the target application under a target development framework, wherein the business logic code indicates the function of the target application, the at least one appearance code indicates at least one appearance of the target application, and the at least one appearance corresponds to at least one terminal type;

the determining module is used for determining rendering-free codes of the target application under the target development framework based on the business logic codes;

And the organizing module is used for organizing the rendering-free code and the at least one appearance code to obtain the complete code of the target application under the target development framework.

10. The apparatus of claim 9, wherein the determining module is specifically configured to:

determining a function name of at least one logic function in the service logic code, a parameter name of at least one parameter corresponding to the at least one logic function respectively and an attribute name of each parameter in the at least one parameter;

and filling the non-rendering template corresponding to the target development framework based on the function name of the at least one logic function, the parameter name of the at least one parameter, the attribute name of each parameter and the storage path of the business logic code, so as to obtain the non-rendering code of the target application under the target development framework.

11. The apparatus of claim 10, wherein the business logic code comprises a logic code annotation and a logic code ontology; the determining module is specifically configured to:

acquiring the function name of the at least one logic function from the logic code body;

and acquiring the parameter name of at least one parameter and the attribute name of each parameter corresponding to the at least one logic function from the logic code annotation.

12. The apparatus of any of claims 9-11, wherein the target application is a Web application, the target development framework is a Vue framework, the target application includes at least one component, and the at least one appearance code indicates at least one appearance of the at least one component; the organization module is specifically configured to:

determining a component name of a sub-component contained in the at least one component and an attribute name of the at least one component based on the at least one appearance code;

and filling a code adaptation template corresponding to the target development framework based on the attribute name of the at least one component, the component name of the sub-component and the storage path of the rendering-free code, so as to obtain the complete code of the target application under the target development framework.

13. The apparatus of claim 12, wherein each appearance code of the at least one appearance code comprises an appearance code annotation; the organization module is specifically configured to:

and acquiring the component name of the sub-component and the attribute name of the at least one component from the appearance code annotation.

14. The apparatus of any of claims 9-11, wherein the target application is a Web application, the target development framework is a act framework, the target application includes at least one component, and the at least one appearance code indicates at least one appearance of the at least one component; the organization module is specifically configured to:

Determining an attribute name of the at least one component based on the at least one appearance code;

determining the function name of at least one logic function in the service logic code;

and filling a code adaptation template corresponding to the target development framework based on the attribute name of the at least one component, the function name of the at least one logic function and the storage path of the rendering-free code so as to obtain the complete code of the target application under the target development framework.

15. The apparatus of claim 14, wherein each appearance code of the at least one appearance code comprises an appearance code body or comprises the appearance code body and an appearance code annotation; the organization module is specifically configured to:

acquiring an attribute name of the at least one component from the appearance code body when the appearance code includes the appearance code body;

and acquiring the attribute name of the at least one component from the appearance code body or the appearance code annotation when the appearance code comprises the appearance code body and the appearance code annotation.

16. The apparatus of any of claims 9-15, wherein the business logic code is in the form of a cori function, and the business logic code and the at least one appearance code are in JavaScript language.

17. A cluster of computing devices, the cluster of computing devices comprising at least one computing device, each computing device comprising a processor and a memory;

the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the cluster of computing devices to perform the method of any of claims 1-8.

18. A computer readable storage medium, characterized in that the storage medium comprises computer program instructions which, when executed by a cluster of computing devices, perform the method according to any of claims 1-8.

19. A computer program, characterized in that the instructions, when executed by a cluster of computing devices, cause the cluster of computing devices to perform the method of any of claims 1-8.