Data processing method, device and electronic equipment of business development component

Abstract

The application discloses a data processing method and device of a business development component and electronic equipment, relates to the technical field of computers, and comprises the following steps: receiving a component access request, registering a to-be-accessed business development component according to component information; aggregating the type of the registered to-be-accessed business development component into a component type data packet of a business database; updating the component type data packet in the business database, and accessing the updated component type data packet to a general component. The technical scheme provided in the application can realize automatic access of a business SDK, improve the business development efficiency, automatically aggregate the type of the business SDK, and display the type of the loaded business SDK based on the component type data packet in the general component in real time when the business loads the business SDK by calling the general component, so that the accuracy of loading of the business development component can be ensured.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a data processing method, apparatus and electronic device for a business development component. Background Technology

[0002] With the development of computer technology, in order to facilitate business development for R&D personnel, business development components, namely business SDKs (Software Development Kits), can be introduced to assist in business development.

[0003] Generally, in related technologies, during business development, if a corresponding SDK exists for the business logic, it can be directly integrated without writing code for that functionality. However, integrating a typical business SDK requires developers to manually connect it by modifying code and obtaining the static resource address returned by the integration system from the person in charge of the general components. Furthermore, this integration method is not only inefficient but also fails to identify the type of the business component during development, potentially leading to errors by developers. Summary of the Invention

[0004] This application provides a data processing method, apparatus, device, storage medium, computer program product, and private cloud business development component access system for business development components. It can realize the automatic access of business development components and lay the data foundation for displaying the corresponding type when loading business development components in the future, thereby improving the development efficiency and accuracy of business development components.

[0005] On the one hand, this application provides a data processing method for a business development component, the method comprising:

[0006] Receive a component access request, the component access request including: component information of the business development component to be accessed;

[0007] Register the development components for the services to be integrated based on the component information;

[0008] The types of the registered business development components to be integrated are aggregated into the component type data packet of the business database; wherein, the component type data packet includes the types corresponding to different business development components and the mapping relationship between different business development components and types;

[0009] Update the component type data packet in the business database and connect the updated component type data packet to the general component so that when the business loads the business development component to be connected, the type corresponding to the business development component to be connected can be displayed.

[0010] On the other hand, a data processing device for a business development component is provided, the device comprising:

[0011] The request receiving module is used to receive component access requests, which include component information of the business development component to be accessed;

[0012] The registration module is used to register the development components of the service to be integrated based on the component information.

[0013] The type aggregation module is used to aggregate the types of the registered business development components to be accessed into the component type data packet of the business database; wherein, the component type data packet includes the types corresponding to different business development components and the mapping relationship between different business development components and types;

[0014] The type insertion module is used to update the component type data package in the business database and connect the updated component type data package to the general component so that when the business loads the business development component to be connected, the type corresponding to the business development component to be connected can be displayed.

[0015] On the other hand, an electronic device is provided, including: a processor;

[0016] Memory used to store the processor's executable instructions;

[0017] The processor is configured to execute the instructions to implement the data processing method of the business development component described in any of the preceding claims.

[0018] On the other hand, a computer-readable storage medium is provided, which, when the instructions in the storage medium are executed by the processor of an electronic device, enables the electronic device to perform the data processing method of any of the above-described business development components.

[0019] On the other hand, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the data processing method of the business development component provided in the various optional implementations described above.

[0020] On the other hand, a private cloud business development component access system is provided, the system including: private cloud, continuous integration deployment component, business database, general components, and business terminal;

[0021] The private cloud is used to receive component access requests and register the business development components to be accessed to the private cloud according to the component access requests.

[0022] The continuous integration deployment component is used to trigger the automatic access process of the business development component after the business development component to be accessed has been registered.

[0023] The business database is used to store business development components registered to the private cloud, and to aggregate the types of business development components registered to the private cloud into component type data packets;

[0024] The general component is used to access the component type data packet for business development purposes;

[0025] The business terminal is used to load the business development component by calling the general component. When the business terminal calls the general component and selects the business development component to be loaded, it displays the type of the business development component to be loaded.

[0026] The data processing method, apparatus, equipment, storage medium, computer program product, and private cloud business development component access system provided in this application have the following technical effects:

[0027] The data processing method for business development components provided in this application, upon receiving an access request for a new business SDK, can register the new business SDK based on the access request. After registration, it triggers an automatic business SDK access process, thereby integrating the business SDK into the system. It also extracts the type definition of the business SDK, aggregates the type of the new business SDK into the component type data package in the business database, and then updates the component type data package in the general components. This achieves automated access to business SDKs, improving business development efficiency. Furthermore, by automatically aggregating the types of business SDKs, when a business loads a business SDK by calling a general component, it can automatically display the type of the loaded business SDK in real time based on the component type data package in the general components, improving the accuracy of business development component loading. Attached Figure Description

[0028] To more clearly illustrate the technical solutions and advantages in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0029] Figure 1 This is a schematic diagram of the application environment for a data processing method for a business development component provided in an embodiment of this application;

[0030] Figure 2 This is a flowchart illustrating the process of manually integrating a business SDK in a private cloud scenario example provided in this manual.

[0031] Figure 3 This is a flowchart illustrating a data processing method for a business development component provided in an embodiment of this application;

[0032] Figure 4 This is a schematic diagram of the interface for a business SDK access request in one embodiment of this specification;

[0033] Figure 5 This is a flowchart illustrating a data processing method for a business development component in a private cloud scenario, as described in one embodiment of this specification.

[0034] Figure 6 This is a schematic diagram of the component registration process in a private cloud scenario in one embodiment of this specification;

[0035] Figure 7 This is a schematic diagram illustrating the principle of type aggregation of the business SDK in one embodiment of this specification;

[0036] Figure 8 This is a schematic diagram illustrating the principle of component type data packet update for a general component in one embodiment of this specification;

[0037] Figure 9 This is a schematic diagram of the return process of a business SDK type in one embodiment of this specification;

[0038] Figure 10 This is a schematic diagram of the structure of a data processing device for a business development component provided in an embodiment of this application;

[0039] Figure 11 This is a block diagram of an electronic device for data processing in a business development component, provided in an embodiment of this application.

[0040] Figure 12 This is a block diagram of another electronic device for data processing of a business development component provided in an embodiment of this application. Detailed Implementation

[0041] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0042] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0043] Please see Figure 1 , Figure 1 This is a schematic diagram of the application environment of a data processing method for a business development component provided in an embodiment of this application. The application environment may include at least a server 100 and a terminal 200.

[0044] In an optional embodiment, server 100 can be used for data processing of business development components. Server 100 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.

[0045] In an optional embodiment, terminal 200 can be used to provide access services to users and for preprocessing in the data processing of business development components such as resource registration, operation registration, role registration, and role authorization. Specifically, terminal 200 can be, but is not limited to, electronic devices such as smartphones, desktop computers, tablets, laptops, smart speakers, digital assistants, augmented reality (AR) / virtual reality (VR) devices, smart wearable devices, in-vehicle terminals, and smart TVs; it can also be software running on the aforementioned electronic devices, such as applications and mini-programs. The operating system running on the electronic device in this embodiment can include, but is not limited to, Android, iOS, Linux, and Windows systems.

[0046] In addition, it should be noted that, Figure 1 The example shown is merely an application environment for a data processing method of a business development component, and the embodiments in this specification are not limited to the above.

[0047] In the embodiments described in this specification, the server 100 and the terminal 200 can be directly or indirectly connected via wired or wireless communication, and this application does not impose any restrictions on this.

[0048] The data processing of the business development components in the embodiments of this specification can be applied to private cloud scenarios. A private cloud is a cloud infrastructure and hardware / software resources created within a firewall, allowing various departments within an organization or enterprise to share resources within a data center. Creating a private cloud typically involves cloud equipment (IaaS, Infrastructure as a Service) software, in addition to hardware resources. Private cloud computing also comprises three layers: cloud hardware, cloud platform, and cloud services. The difference is that cloud hardware consists of the user's own personal computer or server, rather than the cloud computing vendor's data center. Cloud computing vendors build data centers to provide public cloud services to millions of users, thus requiring hundreds of thousands or even millions of servers. For individuals, private cloud computing only serves close friends and family; for enterprises, it only serves their own employees, customers, and suppliers. Therefore, the personal computers or servers of individuals or enterprises are sufficient to provide cloud services.

[0049] In the embodiments of this specification, a business development component can be understood as a business SDK, and a business SDK can be understood as a sub-component of a business component. A component can be understood as a simple encapsulation of data and methods. A business component can be understood as a method with specific business functions. For example, a business component can be a page, and a business SDK can be understood as a component within that page. For instance, if the business component is a login page, the business SDK can be the login button component within that page. Generally, in a private cloud scenario, during business development, if a business SDK is to be used, it needs to be integrated into a general component of the private cloud system so that the business can access the business SDK by calling the general component. Figure 2 This is a flowchart illustrating the manual integration process of a business SDK in a private cloud scenario example, as shown in this manual. Figure 2 As shown, after the business developers have completed the development of the business SDK, they need to register it in the private cloud. The private cloud will return the resource address of the business SDK. The business developers need to take the returned static resource address to the person in charge of the general SDK, i.e. the general component, and manually integrate the business SDK by modifying the code. Only then can the business developers load and use the registered business SDK through the general component.

[0050] As can be seen, in the above scenarios, the integration of the business SDK requires manual intervention, which is inefficient and prone to errors.

[0051] This specification provides a data processing solution for business development components, which enables business SDKs to be automatically integrated into general components. At the same time, it aggregates the types of business SDKs so that business users can receive the corresponding type in real time, achieving a real-time prompt effect. This not only improves the efficiency of business development component integration but also enhances the accuracy of business development.

[0052] The following describes a data processing method for a business development component according to this application. Figure 3 This is a flowchart illustrating a data processing method for a business development component provided in an embodiment of this application. This specification provides method operation steps as shown in the embodiments or flowcharts, but based on conventional or non-inventive labor, more or fewer operation steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only execution order. In actual system or server product execution, the method can be executed sequentially according to the embodiments or drawings, or in parallel (e.g., in a parallel processor or multi-threaded processing environment). Specifically, as shown... Figure 3 As shown, the method may include:

[0053] S302: Receive a component access request. The component access request includes: component information of the business development component to be accessed.

[0054] In the specific implementation process, when developers need to develop a business SDK, they only need to focus on the business-side development and the business SDK development. After the business SDK development is completed, a component access request can be sent to the private cloud access system or other component access systems, and the relevant component information, i.e., component information, can be completed. The component access request may include component information related to the business development component to be accessed, such as: component name, Git information, resource subdirectories, etc. Git can be understood as a code management tool, an open-source distributed version control system (vcs). Depending on actual needs, the component information may also include other content. Users can supplement or fill in other relevant information when registering the business SDK to the system, as needed. This specification does not impose specific limitations on the embodiments.

[0055] Figure 4 This is a schematic diagram of the interface for a business SDK access request in one embodiment of this specification, such as... Figure 4As shown, after developing the business SDK, developers can fill in the Git configuration and routing configuration information of the business SDK to be connected in the access system, such as the private cloud access system. This completes the component information of the business SDK to be connected, so that it can be used when registering the business SDK to the private cloud system later. Of course, other information related to the business SDK can also be filled in as needed. This embodiment of the specification does not make specific limitations.

[0056] Step 304: Register the business development components to be integrated based on the component information.

[0057] In the actual real-time process, upon receiving a component access request, the system can register the business development component to be accessed in the access system based on the component information for subsequent use. For example, in some scenario examples in this manual, the business SDK can be registered to the private cloud component cluster. Generally, after registration, the access system will return the static resource address, Git repository information, etc., of the business SDK for subsequent business calls. After completing the registration of the business development component, the access system can inject the Git repository information and static resource address of the business development component into the pipeline as environment variables, triggering the automatic access process of the business development component.

[0058] In some embodiments of this specification, CI / CD (Continuous Integration, Continuous Deployment) components can be added to the access system, such as a private cloud access system, to automatically trigger the access process of business development components. CI / CD can be understood as a method of frequently delivering applications to customers by introducing automation during the application development phase. After completing automated processes such as building, unit testing, and integration testing, CI / CD can automatically publish verified code to the enterprise's own repository. Continuous deployment aims to establish a codebase that can deploy features from the development environment to the production environment at any time. During continuous deployment, each step involves test automation and code release automation. At the end of the process, the operations team can quickly and easily deploy the application to the production environment.

[0059] Figure 5 This is a flowchart illustrating a data processing method for a business development component in a private cloud scenario, as described in one embodiment of this specification. Figure 5 As shown, the fully automated process outlined by the dashed line can be understood as the private cloud access system in the embodiments of this specification, such as... Figure 5As shown, the private cloud access system may include a private cloud, CICD, a business SDK repository (i.e., the business database described in the embodiments of this specification), and general SDKs, i.e., general components. It can be seen that CICD is added to the private cloud access system in the embodiments of this specification. When a developer registers a business SDK to be accessed in the private cloud, CICD can be triggered to automatically complete the subsequent access process of the business SDK. Through the automated process of component access, repetitive tasks are replaced by automation, reducing time costs and thus shortening version release time, thereby improving development efficiency.

[0060] The execution entity of the data processing method of the business development component in the embodiments of this specification can be understood as the access system of the business development component, such as... Figure 5 As shown, in a private cloud scenario, the data processing method execution subject of the business development component described in the embodiments of this specification can be understood as the private cloud access system within the dashed box.

[0061] Furthermore, in the embodiments of this specification, when registering components, the component category can be marked in the component information. As described in the above embodiments, the embodiments of this specification may include business components and business development components, i.e., business SDKs.

[0062] In some embodiments of this specification, registering the service development component to be accessed based on the component information includes:

[0063] If the component category in the component information is a business component, then the business development component to be integrated will be registered according to the component information;

[0064] If the component category in the component information is a business development component, then the business development component to be connected will be registered according to the component information, and the automatic access process of the business development component will be triggered.

[0065] In the specific real-time process Figure 6 This is a schematic diagram of the component registration process in a private cloud scenario, as shown in one embodiment of this specification. Figure 6 As shown, upon receiving a component access request, it's first necessary to determine whether the component category in the request's component information is a business component or a business development component. If it's a business component, the business component is directly registered in the system (e.g., a private cloud), thus completing the business component access. If the component category in the component information is a business development component (i.e., a business SDK), the business SDK needs to be registered in the system, triggering the subsequent automated access process for business development components to aggregate the types of business SDKs. For example... Figure 5As shown, the automated access process for business development components can be understood as the process by which CICD automatically triggers the access of the business SDK to the system and the aggregation of business SDK types after receiving the signal that the business SDK registration is complete. Specifically, this may include: storing the business SDK in the business database, aggregating the types of newly accessed business SDKs into the component type data packet, updating the component type data packet and general components, etc. For details, please refer to the description in the embodiments of this specification.

[0066] like Figure 6 As shown, in a private cloud scenario, after registering the business component or business SDK in the private cloud, it can be understood that the running code of the business component or business SDK is connected to the private cloud system as a private cloud component, which facilitates subsequent business development and use.

[0067] In the registration process of business components and business SDKs, the embodiments in this specification distinguish between the two by component category, thereby enabling different automated data processing for different categories of components, improving data processing efficiency and accuracy.

[0068] In some embodiments of this specification, after registering the component to be connected based on the component information, the method further includes:

[0069] Registered business development components to be integrated are aggregated into the business database through sub-modules.

[0070] In the specific implementation process, after registering the development teams of the services to be integrated with the access system, such as a private cloud system, all business SDKs can be aggregated into this types repository (i.e., the business database) using Git submodules. When a new business SDK is integrated into the system, its runtime code can be added to the business database using submodules. By using submodules, the source code of multiple business SDKs is stored in a single Git repository, and these submodules are unaware of each other's existence. This achieves independence for different business SDKs, does not affect the performance of each business SDK, and ensures that subsequent business SDKs can be used independently and accurately.

[0071] Step 306: Aggregate the types of the registered business development components to be integrated into the component type data packet of the business database; wherein, the component type data packet includes the types corresponding to different business development components and the mapping relationship between different business development components and types.

[0072] In the specific implementation process, after a new business SDK is registered in the private cloud, an automatic access process for business development components is triggered. The access system can aggregate the types of the business development components to be accessed into the component type data package in the business database. The type of a business development component can be understood as the TypeScript type definition of the business SDK. The type of a business SDK can include data such as parameters and their types in various methods of the business SDK, such as whether the parameter type is character or number. The business database can be understood as a database used to store business-related data, such as storing all business SDKs accessed by the access system and their types. The component type data package can be understood as a data package containing all the types of business SDKs stored in the business database. It can include the types corresponding to multiple business SDKs, and can also include the mapping relationship between different business development components and their corresponding types. For example, a directory can be created in the component type data package to store each business SDK and its corresponding type. For instance, the component type data package contains type data A for business SDK1, type data B for business SDK2, type data C for business SDK3, and the mapping relationship between business SDK1, business SDK2, business SDK3 and type data A, B, and C.

[0073] When a new business SDK is integrated into the system, the type data corresponding to the new business SDK can be extracted and added to the component type data package in the business database to achieve aggregation of the new business SDK's types.

[0074] Figure 7 This is a schematic diagram illustrating the principle of type aggregation of the business SDK in one embodiment of this specification, such as... Figure 7 As shown, when integrating a new business SDK, the new business SDK can be integrated into the business database using a submodule approach. At the same time, the type definition of the new business SDK and the type definitions of other existing business SDKs in the business database are exported through a common export, that is, the type definition of the new business SDK and the type definitions of other existing business SDKs are aggregated into a new component type data package, and the new component type data package is published.

[0075] In some embodiments of this specification, the types of registered service development components to be integrated are aggregated into the component type data packet of the service database, including:

[0076] The script iterates through the business development components in the business database, packages the types of business development components to be integrated, and aggregates the packaged types of business development components to be integrated into the component type data package in the business database.

[0077] In the specific implementation process, after the business SDK registration is completed, a script can be used to traverse the business SDKs stored in the business database, package the TypeScript type definitions of newly added business development components to be integrated, and aggregate them into a directory, such as the component type data package in the business database. Then, a single export file can be used to export all type definitions. For example, after receiving a new business SDK integration request, and after the new business SDK has integrated into the system and registered, a script can be used to traverse the business SDKs stored in the business database, package the types of the newly added business SDKs, and add the data packages corresponding to the types of the newly added business SDKs to the component type data packages in the business database, thus completing the aggregation of the types of the newly added business SDKs.

[0078] This embodiment of the specification uses an incremental script approach to peel and aggregate the type definitions of newly integrated business SDKs without requiring additional configuration. This achieves automated identification of the type definitions of business SDKs, thereby providing type suggestions when the business SDKs are called subsequently. This facilitates developers' review, lays a data foundation, and improves the efficiency and accuracy of business development.

[0079] Step 308: Update the component type data package in the business database and connect the subsequent component type data package to the general component so that when the business loads the business development component to be connected, the type corresponding to the business development component to be connected can be displayed.

[0080] In the specific implementation process, the general component (also known as the general SDK) is a front-end general SDK used by the business side, encapsulating general methods for business scenarios such as private cloud scenarios. In some embodiments of this specification, newly generated component type data packages from the business database can be introduced into the general SDK, and the method for asynchronously obtaining the business SDK can be modified synchronously. The business SDK part encapsulates a method for asynchronously pulling business SDK resources and injecting them into the global scope. After integrating a new business SDK and aggregating to obtain a new business SDK component type data package, the component type data packages in the business database can be updated. Each component type data package can have its own version number. When updating the component type data package, the version number and data within the data package can be updated, and the updated component type data package can be published. After generating a new component type data package, the general component can be automatically triggered to update the component type data package, thereby integrating the updated component type data package into the general component, and then publishing the new general component package. On the business side, the required business SDK can be loaded by calling the general component. Based on the component type data package in the general component, the type can be distributed in the general component through generic reflection. That is, when the business side loads the business SDK through the general component, it can display the type corresponding to the loaded business SDK based on the component type data package accessed in the general component. This achieves the requirement of obtaining type prompts in real time during development, avoids development errors, and improves the efficiency and accuracy of business development.

[0081] In some embodiments of this specification, the step of connecting the updated component type data packet to the general component includes:

[0082] Query the latest component type data package version number in the component type data package stored in the business database;

[0083] Submit a merge branch request, and update the component type data packets in the general components based on the latest component type data packet version number found and the merge branch request.

[0084] In the specific implementation process Figure 8 This is a schematic diagram illustrating the principle of component type data packet update for a general component in one embodiment of this specification, as shown below. Figure 8As shown, when a new business SDK is integrated, after aggregating and obtaining the new component type data package in the business database, the business database can publish the new component type data package. At this time, the operation of modifying the component type data package of the general component can be triggered. First, the latest component type data package version number can be queried in the component type data packages stored in the business database. Then, a merge request (MR) is submitted to merge the code. Based on the version of the component type data package in the branch to be merged by the merge request and the latest version of the component type data package in the business database, the component type data package in the general component is updated, and the general component is repackaged and published for use by the business side. The merge request refers to merging the developed code into the desired branch using a merge request method. The recipient of this request is generally the project or team leader or other members. Through the merge request, the latest component type data package can be obtained from the latest developments by the developers and the data stored in the business database, ensuring that the component type data package in the general component is the latest version. This ensures that the business side can use the latest business SDK, laying an accurate data foundation for subsequent business development.

[0085] Figure 9 This is a schematic diagram illustrating the return process of a business SDK type in one embodiment of this specification, such as... Figure 9 As shown in some embodiments of this specification, not only can the type reflected by the type packet be returned based on the component type data packet in the general component, but type slots can also be reserved in the general component for manually specifying the type in the business during the business SDK development phase for development and debugging.

[0086] The data processing method for business development components provided in this specification, upon receiving an access request for a new business SDK, can register the new business SDK based on the access request. After registration, it triggers an automatic business SDK access process, thereby integrating the business SDK into the system. The method also involves extracting the type definition of the business SDK, aggregating the type of the new business SDK into the component type data packet in the business database, and then updating the component type data packet in the general components. This achieves automated access to business SDKs, improving business development efficiency. Furthermore, by automatically aggregating the types of business SDKs, when the business side loads a business SDK by calling the general components, the type of the loaded business SDK can be automatically displayed in real time based on the component type data packet in the general components, improving the accuracy of business development component loading.

[0087] In some embodiments of this specification, the method further includes:

[0088] When a request to invoke the general component is received, the business development component in the general component is displayed.

[0089] In practical implementation, when a business application needs to use a business SDK, it can asynchronously load the required business development components by calling a general component. Upon receiving a call request for a general component from the business application, the application can display the business development components within that general component, providing real-time information on currently supported business SDKs. This allows developers to intuitively understand the available business SDKs, thereby avoiding loading errors and improving the efficiency and accuracy of business development. The display method can be configured according to actual needs; for example, when calling the general component, the names of all available business SDKs can be listed sequentially in the general component's parameters.

[0090] In some embodiments of this specification, the method further includes:

[0091] After displaying the business development components in the general components, based on the business development object to be loaded, the type corresponding to the business development component to be loaded is returned to the corresponding variable from the component type data packet in the general components, and the methods contained in the business development component to be loaded are displayed.

[0092] In the specific implementation process, as described in the above embodiments, the business development object (e.g., the person responsible for business development) can asynchronously load the required business SDK by calling the general component. After calling the general component, the business development object can select the required business SDK from the parameters displayed in the general component or directly input the corresponding parameters. Based on the parameters input by the user or the selected business SDK, the type corresponding to the business development component to be loaded can be returned to the corresponding variable from the component type data package in the general component. At the same time, the methods contained in the business development component to be loaded can also be displayed in the editor to facilitate developers' viewing or code completion during development, avoid developers' input errors, and improve the efficiency and accuracy of business development.

[0093] Referring to the description in the above embodiments, the data processing method of the business development component in the embodiments of this specification can be applied to private cloud scenarios. Generally, in private cloud scenarios, the integration of business SDKs used in business operations is entirely manual. This not only increases the development burden on the business side but also requires the general SDK owner to manually modify the code to maintain the integration table, repackage and release it, and then manually notify the business side development. Furthermore, since the business SDK loading is essentially done by dynamically importing resources through scripts, it's impossible to dynamically analyze the SDK type like with npm packages during local development. This results in the inability to obtain the business SDK's TypeScript type definition when calling the loading method in the business after integration, making it impossible to obtain real-time type hints from the editor, leading to low development efficiency and a high error rate. Figure 5 As shown, the embodiments in this specification can automate the subsequent process of integrating business SDKs into the general SDK by triggering CICD after adding a new business SDK to the private cloud access system. Simultaneously, after aggregating the types of all business SDKs, the general SDK distributes the types via generic reflection, achieving the requirement of real-time type hints during development. The following section combines... Figure 5 This section details the data processing flow of the business SDK in a private cloud scenario:

[0094] When developers need to develop a business SDK, they only need to focus on the business-side development and the business SDK development. Once the business SDK development is complete, the entire process of integrating the business SDK is automated, replacing the previous manual integration. The template framework used when creating a new business SDK can be uniformly modified so that it can separately package the type definitions of the business SDK and integrate them into a single d.ts type definition file.

[0095] 1) After developers complete the development of the business SDK using the modified template framework, they need to complete the relevant information (component name, Git information, resource subdirectories, etc.) in the private cloud, just like with business components. They also need to select the component category as "business SDK" to register the business SDK. See [link to relevant documentation] for details. Figure 4 As shown.

[0096] 2) Component categories can include business components and business SDKs. The former is used for registering business components, and the latter is used for registering business SDKs. If a business SDK is entered, the CI / CD pipeline for business SDK integration will be triggered to perform type aggregation after the component integration is completed. For details, please refer to [link to relevant documentation]. Figure 6 As shown. The differences between business components and business SDKs are detailed in the above embodiments and will not be repeated here.

[0097] 3) The access system will inject the Git repository address of the business SDK and the static resource address after the access is completed into the pipeline as environment variables, and at the same time pull the business SDK large repository, namely the business database described in the embodiments of this specification.

[0098] 4) The Business SDK Repository, as the name suggests, is a repository for storing all business SDK repositories and type packages after type aggregation. The repository uses a central export point to aggregate and export all business SDKs from all sub-modules. Whenever a new business SDK is integrated, its Git repository information is recorded as a sub-module in the repository, and a separate directory is created for that business SDK to store its types. Simultaneously, the new business SDK is packaged into types. After packaging, export statements are inserted into the central export point to complete incremental updates. Finally, the incrementally updated type packages are published. For details, please refer to [link to documentation / reference]. Figure 7 As shown.

[0099] 5) The general SDK (i.e., general components) is a front-end general SDK used on the business side. It encapsulates general methods for private cloud scenarios. The business SDK part encapsulates a set of methods for asynchronously pulling business SDK resources and injecting them into the global scope. Compared to simply encapsulating general pulling methods, by introducing component type data packages and using generic reflection of the types in the business SDK type package (i.e., component type data packages), the pain point of business development not being able to obtain the types is solved. At the same time, as described in the above embodiments, type slots can be reserved in the general components for manually specifying types in the business during the business SDK development phase for development and debugging.

[0100] 6) After the component type data package is published, CICD will receive a signal indicating that the business SDK type package has been published. At this time, a modification and publication operation of the general SDK will be triggered. First, the latest type package version number will be found, then the version number of the type package in the package.json of the general SDK will be updated, and finally a merge request will be submitted to merge the code. After the merge is completed, a packaging and publication operation will be triggered. The new version of the type package will be pulled according to the updated package.json, and then the general SDK will be repackaged and published for use by the business side. The specific process can be referred to the description in the above embodiment, and will not be repeated here.

[0101] 7) Finally, the developer updates the general SDK on the business side. By calling the method to load the business SDK, the developer can obtain the newly developed business SDK type and parameter enumeration. The specific process can be referred to the description in the above embodiment, and will not be repeated here.

[0102] The data processing procedure of the business SDK provided in this specification allows the business side to focus only on the development and integration of the business SDK, and then use it in the business. There is no need to manually copy information for the general SDK manager to integrate. Furthermore, when calling the general SDK to obtain the business SDK, compared to previous methods, the types within the business SDK can be obtained, and corresponding Lint (a program inspection tool) prompts can be obtained during development, reducing errors caused by manually entering method names. For the general SDK manager, the process of manually modifying code and repackaging for release is reduced, transforming it into a fully automated process. It also adds the functionality of reflecting the business SDK type package type, providing developers with a better development experience and improving the accuracy and efficiency of business development.

[0103] Based on the data processing method for the business development component described above, one or more embodiments of this specification also provide a client and server for the data processing of the business development component. The client and server may include devices (including distributed systems), software (applications), modules, components, servers, clients, etc., that use the methods described in the embodiments of this specification, combined with necessary implementation hardware. Based on the same innovative concept, the devices in one or more embodiments provided in this specification are as described in the following embodiments. Since the implementation schemes and methods for solving the problem by the devices are similar, the implementation of specific devices in the embodiments of this specification can refer to the implementation of the foregoing methods, and repeated details will not be repeated. As used below, the terms "unit" or "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0104] As can be seen from the technical solutions provided in the embodiments of this specification above, the embodiments of this application also provide a data processing device for a business development component. Figure 10 This is a schematic diagram of the structure of a data processing device for a business development component provided in an embodiment of this application, such as... Figure 10 As shown, the above-mentioned device includes:

[0105] The request receiving module 1010 is used to receive component access requests, which include component information of the business development component to be accessed.

[0106] Registration module 1020 is used to register the business development components to be integrated based on the component information;

[0107] The type aggregation module 1030 is used to aggregate the types of registered business development components to be integrated into the component type data packet of the business database; wherein, the component type data packet includes the types corresponding to different business development components and the mapping relationship between different business development components and types;

[0108] The type insertion module 1040 is used to update the component type data packet in the business database and connect the updated component type data packet to the general component so that when the business loads the business development component to be connected, the type corresponding to the business development component to be connected is displayed.

[0109] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operations has been described in detail in the embodiments related to the method, and will not be elaborated upon here. The apparatus in the above embodiments may also include other implementation methods based on the description of the method embodiments; specific implementation methods can be referred to the description of the relevant method embodiments, and will not be repeated here.

[0110] Figure 11 This is a block diagram of an electronic device for data processing in a business development component, provided in an embodiment of this application. The electronic device can be a terminal, and its internal structure diagram can be as follows: Figure 11 As shown, the electronic device includes a processor, memory, network interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements a data processing method for a business development component. The display screen can be a liquid crystal display (LCD) or an e-ink display. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the device's casing, or an external keyboard, touchpad, or mouse.

[0111] Figure 12 This is a block diagram of another electronic device for data processing in a business development component, provided in an embodiment of this application. The electronic device can be a server, and its internal structure diagram can be as follows: Figure 12As shown, the electronic device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements a data processing method for a business development component.

[0112] Those skilled in the art will understand that Figure 11 or Figure 12 The structure shown is merely a block diagram of a portion of the structure related to the present disclosure and does not constitute a limitation on the electronic device to which the present disclosure is applied. A specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0113] like Figure 5 As shown in some embodiments of this specification, a private cloud business development component access system may also be provided, the system comprising: a private cloud, a continuous integration deployment component, a business database, general components, and a business terminal;

[0114] The private cloud is used to receive component access requests and register the business development components to be accessed to the private cloud according to the component access requests.

[0115] The continuous integration deployment component is used to trigger the automatic access process of the business development component after the business development component to be accessed has been registered.

[0116] The business database is used to store business development components registered to the private cloud, and to aggregate the types of business development components registered to the private cloud into component type data packets;

[0117] The general component is used to access the component type data packet for business development purposes;

[0118] The business terminal is used to load the business development component by calling the general component. When the business terminal calls the general component and selects the business development component to be loaded, it displays the type of the business development component to be loaded.

[0119] In this context, the private cloud, continuous integration deployment components, business database, and general components can be understood as the private cloud access system described in the above embodiments, and the business end can be understood as the client for business development. The specific methods by which each module in the above system performs its operations have been described in detail in the embodiments related to this method, and will not be elaborated upon here. Based on the description of the method embodiments, the above system may also include other implementation methods; specific implementation methods can be referred to the descriptions of the relevant method embodiments, and will not be repeated here.

[0120] In an exemplary embodiment, an electronic device is also provided, including: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement a data processing method of a business development component as described in the embodiments of this disclosure.

[0121] In an exemplary embodiment, a computer-readable storage medium is also provided, wherein when the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the data processing method of the business development component in the embodiments of this disclosure.

[0122] In an exemplary embodiment, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the data processing method of the business development component provided in the various optional implementations described above.

[0123] It is understood that in the specific implementation of this application, user-related data is involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0124] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0125] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0126] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A data processing method for a business development component, characterized in that, The method includes: Receive a component access request, the component access request including: component information of the service SDK to be accessed; Register the SDK for the service to be accessed based on the component information; The types of the registered service SDKs to be integrated are aggregated into the component type data packet of the service database; wherein, the component type data packet includes the types corresponding to different service SDKs and the mapping relationship between different service SDKs and types; Update the component type data package in the business database and connect the updated component type data package to the front-end general SDK so that when the business loads the business SDK to be connected, it can display the type corresponding to the business SDK to be connected. The method further includes adding a CICD component to the access system, wherein the CICD component is used to trigger the automatic access process of the service SDK after the service SDK to be accessed is registered.

2. The method according to claim 1, characterized in that, After registering the SDK for the service to be accessed based on the component information, the method further includes: The registered business SDKs to be integrated are aggregated into the business database through sub-modules.

3. The method according to claim 1, characterized in that, The step of aggregating the types of the registered service SDKs to be integrated into the component type data packet of the service database includes: The script iterates through the business SDKs in the business database, packages the types of the business SDKs to be integrated, and aggregates the packaged types of the business SDKs to be integrated into the component type data package of the business database.

4. The method according to claim 1, characterized in that, The step of integrating the updated component type data package into the front-end general SDK includes: Query the latest component type data packet version number in the component type data packets stored in the business database; Submit a merge branch request, and update the component type data package in the front-end general SDK according to the latest component type data package version number found and the merge branch request.

5. The method according to claim 1, characterized in that, The step of registering the service SDK to be accessed based on the component information includes: If the component category in the component information is a business SDK, then the business SDK to be accessed will be registered according to the component information, and the automatic access process of the business SDK will be triggered.

6. The method according to claim 1, characterized in that, The method further includes: When a request to call the general front-end SDK is received, the business SDK in the general front-end SDK is displayed.

7. The method according to claim 6, characterized in that, The method further includes: After displaying the business SDK in the general front-end SDK, based on the business SDK to be loaded determined by the business development object, the type corresponding to the business SDK to be loaded is returned to the corresponding variable from the component type data package in the general front-end SDK, and the methods contained in the business SDK to be loaded are displayed.

8. A data processing device for a business development component, characterized in that, The device includes: The request receiving module is used to receive component access requests, which include component information of the service SDK to be accessed. The registration module is used to register the SDK of the service to be accessed based on the component information; The type aggregation module is used to aggregate the types of the registered business SDKs to be accessed into the component type data packet of the business database; wherein, the component type data packet includes the types corresponding to different business SDKs and the mapping relationship between different business SDKs and types; The type insertion module is used to update the component type data package in the business database and connect the updated component type data package to the front-end general SDK so that when the business loads the business SDK to be connected, it can display the type corresponding to the business SDK to be connected. The device is further configured to: add a CICD component to the access system, wherein the CICD component is configured to trigger the automatic access process of the service SDK after the service SDK to be accessed is registered.

9. The apparatus according to claim 8, characterized in that, The device is also used for: After registering the SDK for the service to be accessed based on the component information, the registered SDK for the service to be accessed is aggregated into the service database through sub-modules.

10. The apparatus according to claim 8, characterized in that, The type aggregation module is also used for: The script iterates through the business SDKs in the business database, packages the types of the business SDKs to be integrated, and aggregates the packaged types of the business SDKs to be integrated into the component type data package of the business database.

11. The apparatus according to claim 8, characterized in that, The type insertion module is also used for: Query the latest component type data packet version number in the component type data packets stored in the business database; Submit a merge branch request, and update the component type data package in the front-end general SDK according to the latest component type data package version number found and the merge branch request.

12. The apparatus according to claim 8, characterized in that, The registration module is also used for: If the component category in the component information is a business SDK, then the business SDK to be accessed will be registered according to the component information, and the automatic access process of the business SDK will be triggered.

13. The apparatus according to claim 8, characterized in that, The device is also used for: When a call request is received from the general front-end SDK, the business SDK in the general front-end SDK is displayed.

14. The apparatus according to claim 13, characterized in that, The device is also used for: After displaying the business SDK in the general front-end SDK, based on the business SDK to be loaded determined by the business development object, the type corresponding to the business SDK to be loaded is returned to the corresponding variable from the component type data package in the general front-end SDK, and the methods contained in the business SDK to be loaded are displayed.

15. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the data processing method of the business development component as described in any one of claims 1 to 7.

16. A computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device is able to perform the data processing method of the business development component as described in any one of claims 1 to 7.

17. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads and executes the computer instructions from the computer-readable storage medium, causing the computer device to perform the data processing method of the business development component as described in any one of claims 1 to 7.

18. A private cloud service development component access system, characterized in that, The system includes: a private cloud, continuous integration and deployment components, a business database, a general front-end SDK, and a business application. The private cloud is used to receive component access requests and register the service SDK to be accessed to the private cloud according to the component access requests; The continuous integration deployment component is used to trigger the automatic access process of the business SDK after the business SDK to be accessed is registered. The business database is used to store business SDKs registered to the private cloud, and aggregates the types of business SDKs registered to the private cloud into component type data packets; the component type data packets include the types corresponding to different business SDKs and the mapping relationship between different business SDKs and types. The general-purpose front-end SDK is used to access the component type data packets for business development purposes; The business terminal is used to load the business SDK by calling the front-end general SDK. When the business terminal calls the front-end general SDK and selects the business SDK to be loaded, it displays the type of the business SDK to be loaded.

Images