Unified development method and system supporting high-low code dynamic fusion arrangement

Abstract

The application relates to the technical field of software development, and discloses a unified development method and system supporting high and low code dynamic fusion arrangement, which comprises the following steps: acquiring view configuration data corresponding to each view in a business application, determining corresponding view types, and establishing a unified route registration relationship containing low code views and high code views; determining view resources corresponding to each view, and generating view loading configurations corresponding to the view types; receiving a business access request, determining a target view according to the unified route registration relationship, and loading corresponding low code view resources or high code view resources; combining the loaded low code views and high code views in a unified application running environment, and realizing the collaborative running of high and low code views in the business application based on the unified route registration relationship. The application scheme realizes the fusion arrangement and continuous collaborative running of low code views and high code views in the same business application.

Description

Technical Field

[0001] This invention relates to the field of software development technology, and in particular to a unified development method and system that supports dynamic integration and orchestration of high and low code. Background Technology

[0002] As enterprise business systems continue to expand, a single development model is increasingly unable to balance delivery efficiency with the implementation of complex functions. Low-code development typically generates forms, lists, and basic business pages based on page metadata, which can shorten the development cycle of routine functions. However, for complex interactions, professional graphic displays, and high-performance processing scenarios, high-code approaches are still required for customized development. Existing business systems usually build low-code and high-code pages separately and then connect them through external links, embedded pages, or independent subsystems. Because the two types of pages use different resource description and loading methods, there is a lack of unified association in terms of page organization, route matching, and runtime context. This can easily lead to problems such as scattered page entry points, inconsistent resource loading paths, and the inability to continuously pass login status or business parameters during navigation.

[0003] While some development platforms allow configuring low-code and high-code pages within the same project, they typically maintain these two types of pages only during the development phase, calling them at runtime according to their respective fixed loading entry points. When a business access request arrives, the system struggles to determine the type of the target page based on unified routing information and further match page metadata or program resources. As business functions adjust, the navigation relationships and resource addresses between pages need to be modified separately, easily leading to inconsistencies between routing configurations and actual page resources. Furthermore, if both types of pages enter the same business application, the lack of a unified view container and a common runtime context means that user permissions, access parameters, and business states still need to be repeatedly initialized, making it difficult to form a continuous business operation process.

[0004] Therefore, there is an urgent need for a unified development method that supports dynamic integration and orchestration of low-code and high-code views, uniformly registers low-code and high-code views, forms corresponding resource loading configurations based on view types, and completes differentiated loading and collaborative operation in a unified application runtime environment. Summary of the Invention

[0005] This invention provides a unified development method and system that supports dynamic fusion and orchestration of high and low code views, thereby at least solving the problem in the prior art where the low code view and the high code view are separated and it is difficult to complete resource loading and collaborative operation under a unified routing system.

[0006] To achieve the above objectives, a first aspect of the present invention provides a unified development method that supports dynamic fusion and orchestration of high- and low-code, the method comprising the following steps: Obtain view configuration data corresponding to each view in the business application, determine the corresponding view type based on the view configuration data, and establish a unified routing registration relationship that includes low-code views and high-code views; Based on the unified routing registration relationship, determine the view resources corresponding to each view, and generate the view loading configuration corresponding to the view type; Receive a business access request, determine the target view according to the unified routing registration relationship, and load the corresponding low-code view resource or high-code view resource according to the view loading configuration; The loaded low-code view and high-code view are combined in a unified application runtime environment, and the high- and low-code views in business applications are made to run collaboratively based on a unified routing registration relationship.

[0007] To achieve the above objectives, a second aspect of the present invention also provides a unified development system supporting dynamic fusion and orchestration of high- and low-code, the system being used to execute the above-described unified development method supporting dynamic fusion and orchestration of high- and low-code, the system comprising: The acquisition module is used to obtain the view configuration data corresponding to each view in the business application, determine the corresponding view type based on the view configuration data, and establish a unified routing registration relationship that includes low-code views and high-code views. The configuration module is used to determine the view resources corresponding to each view based on the unified routing registration relationship, and to generate the view loading configuration corresponding to the view type; The loading module is used to receive business access requests, determine the target view according to the unified routing registration relationship, and load the corresponding low-code view resources or high-code view resources according to the view loading configuration. The combination module is used to combine the loaded low-code view and high-code view in a unified application runtime environment, and to enable the high- and low-code views to run collaboratively in business applications based on a unified routing registration relationship.

[0008] The beneficial effects of this invention are as follows: By uniformly identifying, registering, and routing low-code and high-code views in business applications, a correspondence between view types, view resources, and loading methods can be established within the same routing system. Upon arrival of a business access request, the corresponding view can be accurately matched based on the target route, and the target view can be generated by calling either the page metadata parsing mechanism or the program resource loading mechanism, avoiding separate deployment and independent redirection of the two types of views due to different resource organization methods. Furthermore, by organizing the two types of views within a unified application runtime environment and maintaining continuous routing relationships, low-code and high-code views can share application entry points and runtime contexts, thereby reducing redundant configuration and state re-initialization, and improving the integration efficiency and operational continuity of complex business functions. Attached Figure Description

[0009] Figure 1 This is a flowchart illustrating the execution of a unified development method that supports dynamic fusion and orchestration of high and low code in an embodiment of the present invention. Figure 2 This is a schematic diagram illustrating the differentiated loading of low-code views and high-code views in an embodiment of the present invention; Figure 3 This is a system architecture diagram of a unified development system that supports dynamic fusion and orchestration of high and low code in an embodiment of the present invention. Detailed Implementation

[0010] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0011] This invention provides a unified development method that supports dynamic fusion and orchestration of high- and low-code, referring to... Figure 1 , Figure 1 This is a flowchart illustrating a unified development method that supports dynamic fusion and orchestration of high and low code in an embodiment of the present invention.

[0012] In this embodiment, a unified development method that supports dynamic fusion and orchestration of high- and low-code languages ​​includes the following steps: S1: Obtain the view configuration data corresponding to each view in the business application, determine the corresponding view type based on the view configuration data, and establish a unified routing registration relationship that includes low-code views and high-code views.

[0013] Specifically, the process involves obtaining view configuration data corresponding to each view in the business application, and determining the corresponding view type based on the view configuration data. This includes: obtaining the view identifier, view routing information, and view resource description information corresponding to each view in the business application; determining the resource generation method of the corresponding view based on the view resource description information; determining the corresponding view as a low-code view when the view resource description information corresponds to a page generated based on page metadata; and determining the corresponding view as a high-code view when the view resource description information corresponds to a page loaded based on program resources. Finally, the process involves generating corresponding view registration information based on the view routing information, the view type, and the view resource description information.

[0014] Furthermore, establishing a unified route registration relationship that includes low-code views and high-code views includes: obtaining view registration information corresponding to each view; determining the route node corresponding to each view based on the view routing information in the view registration information; associating the view type and view resource description information corresponding to each view to the corresponding route node to form a view registration item corresponding to each route node; organizing the view registration items according to the page jump relationship between each route node to generate the unified route registration relationship.

[0015] Specifically, the view registration items are organized according to the page navigation relationships between each routing node to generate the unified routing registration relationship, including: obtaining the page access paths and navigation associations between each routing node; determining the entry routes and associated routes corresponding to each routing node based on the page access paths, and establishing associations between different routing nodes based on the navigation associations; binding the view registration items corresponding to each routing node with the corresponding entry routes and associated routes to generate a unified routing registration relationship containing routing nodes, view types, view resource description information, and routing associations.

[0016] In this embodiment of the invention, view configuration data corresponding to each view to be orchestrated within a business application is obtained. The view configuration data includes at least a view identifier, view routing information, and view resource description information. The view identifier distinguishes different business pages; the view routing information represents the path corresponding to accessing the business page; and the view resource description information represents the resource type, resource location, and resource entry point on which the business page depends. Specifically, the view identifier uses a unique character encoding within the business application; the view routing information uses a path structure separated by " / ", for example, " / customer / list" for the customer list view and " / customer / detail" for the customer details view; and the view resource description information records the resource generation method, resource address, and resource entry point identifier.

[0017] The resource generation method for a corresponding view is determined based on its resource description information. When the view resource description information includes a page model identifier, component tree description, field configuration, and event configuration, and the page structure is generated by parsing the page model, the corresponding view is identified as a low-code view. Taking the customer list view as an example, its resource description information includes the page model identifier `page_customer_list`, component tree configuration, and data source configuration. After parsing the page metadata, list components, query components, and pagination components are formed; therefore, this customer list view is marked as a low-code view. When the view resource description information includes a program module entry point, program package address, and a list of dependent resources, and the page is formed by loading the program module, the corresponding view is identified as a high-code view. For example, the resource description information for a 3D device display view includes the module entry point "equipment3d / index.js", style resources, and service call configuration. An interactive page is formed by loading the corresponding program resources; therefore, this view is marked as a high-code view.

[0018] After determining the view type, the view routing information, view type, and view resource description information are combined to generate view registration information. View registration information includes at least the view identifier, route path, view type, resource address, and resource entry point. The resource entry point for low-code views points to page metadata, while the resource entry point for high-code views points to the application module. Different views use a unified registration data structure, where fields unrelated to the current view type are left empty, thus ensuring a consistent data reading method in subsequent route matching processes.

[0019] Furthermore, the corresponding route nodes are determined based on the view routing information in each view's registration information. Route nodes are set according to the page hierarchy and access path in the business application; the root path corresponds to the entry route, and sub-paths following the root path correspond to associated routes. For example, " / customer" is the customer business entry route, and " / customer / list" and " / customer / detail" are associated routes, respectively. The corresponding entry route and associated routes are determined based on the page access path corresponding to each route node, and the view type and view resource description information of each view are associated with the corresponding route node to form view registration items.

[0020] View registration items are organized according to the page navigation relationships between each routing node. The page navigation relationships are determined based on the target path, menu entry, and business operation links in the page configuration. For example, if the details operation in the customer list view points to " / customer / detail", then a navigation association is established between the routing node corresponding to the customer list and the routing node corresponding to the customer details. Based on these navigation associations, associations are established between different routing nodes, and the view registration items corresponding to each routing node are associated with their corresponding entry routes and associated routes. The resulting unified routing registration relationship includes each routing node, the view registration items corresponding to each routing node, and the navigation associations between different routing nodes. During subsequent business access, the corresponding routing node can be determined based on the target access path, and the view type and view resources associated with that routing node can be further obtained. In other embodiments, view routing information uses hash routing or segmented routing, which still falls within the protection scope of the unified routing registration relationship described in this embodiment.

[0021] Step S2: Determine the view resources corresponding to each view based on the unified routing registration relationship, and generate the view loading configuration corresponding to the view type.

[0022] Specifically, the process involves determining the view resources corresponding to each view based on the unified routing registration relationship and generating a view loading configuration corresponding to the view type. This includes: obtaining the view registration item corresponding to each routing node based on the unified routing registration relationship; determining the corresponding view resource based on the view resource description information in the view registration item; matching the corresponding resource loading method based on the view type in the view registration item; generating a low-code view loading configuration based on the corresponding page metadata resource when the view type is a low-code view; generating a high-code view loading configuration based on the corresponding program resource information when the view type is a high-code view; and associating the low-code view loading configuration or the high-code view loading configuration with the corresponding view registration item to generate the view loading configuration.

[0023] In this embodiment of the invention, the view registration items corresponding to each routing node are obtained one by one according to the unified routing registration relationship, and the view type and view resource description information are read from the view registration items. The view resource description information is used to indicate the storage location, resource entry point, and resource composition of the view resources. For low-code views, view resources include page metadata files, component configurations, field configurations, event configurations, and data source configurations; for high-code views, view resources include program module entry points, program package addresses, style resources, and a list of dependent resources.

[0024] When determining the corresponding view resource based on the view resource description information, the resource address and resource entry identifier are read first, and then the resource validity is verified. Resource validity verification includes checking if the resource address is empty, if the resource entry exists, and if the resource type matches the view type. For example, if the view resource description information of a low-code customer list view records the page metadata address "metadata / customerList.json", then that page metadata, along with its associated component configuration and data source configuration, is determined as the corresponding view resource. If the view resource description information of a high-code device display view records the program module entry "equipment3d / index.js", then that program module, along with its dependent style resources and runtime libraries, is determined as the corresponding view resource.

[0025] The resource loading method is matched according to the view type in the view registration item. When the view type is a low-code view, a low-code view loading configuration is generated according to the page metadata parsing method. The low-code view loading configuration includes at least the page metadata address, page model identifier, component parsing order, data source initialization information, and event binding information. For example, when the page model identifier is page_customer_list, the layout information is parsed first, then the query component and list component are loaded, and then the data source and page events are bound.

[0026] When the view type is a high-code view, a high-code view loading configuration is generated according to the program resource loading method. The high-code view loading configuration includes at least the program module entry point, the address of dependent resources, the view mounting location, and the method for receiving initialization parameters. For example, when the program module entry point is "equipment3d / index.js", its dependent runtime libraries and style resources are loaded first, then the module entry point is executed, and the generated view instance is mounted to the corresponding view container.

[0027] Finally, the generated low-code or high-code view loading configuration is associated with the corresponding view registration item, so that the same routing node simultaneously stores the view type, view resources, and loading method of the target view. Upon receiving a subsequent business access request, the corresponding view loading configuration can be directly obtained based on the target routing node. In other embodiments, page metadata is presented as database records, and program resources are presented as independent module packages, still falling within the protection scope of the view resources and loading configurations described in this embodiment.

[0028] Preferably, after generating the view loading configuration, the dependency library identifiers, dependency versions, and global variable declarations in each high-code view program resource are extracted, and the version information of the component runtime library corresponding to each low-code view page metadata is extracted; resource conflicts are determined based on the differences in dependency versions and duplicate global variable names between different views; for each resource conflict, an independent namespace and dependency isolation identifier are written into the corresponding view loading configuration, so that conflicting program resources are loaded in different scopes. For example, when the low-code component runtime library and the high-code chart module depend on different versions of the same chart library, the high-code chart module is mounted to an independent namespace, and its dependency resolution path is limited to avoid page anomalies caused by dependency overriding during the collaborative operation of the two types of views.

[0029] Step S3: Receive the service access request, determine the target view according to the unified routing registration relationship, and load the corresponding low-code view resource or high-code view resource according to the view loading configuration.

[0030] Specifically, receiving a service access request and determining the target view based on the unified routing registration relationship includes: parsing the service access request to obtain the target access path and access parameters; matching the corresponding target route node in the unified routing registration relationship based on the target access path; determining the view type, view resource description information, and corresponding view loading configuration of the target view based on the view registration item corresponding to the target route node; associating the access parameters with the view loading configuration to generate a view loading request corresponding to the target view.

[0031] Furthermore, loading the corresponding low-code view resources or high-code view resources according to the view loading configuration includes: parsing the view loading request to obtain the view type, view resources, and access parameters corresponding to the target view; when the target view is a low-code view, obtaining page metadata according to the corresponding low-code view loading configuration, parsing the page metadata, and performing page initialization and rendering based on the access parameters to generate a low-code target view; when the target view is a high-code view, obtaining program resources according to the corresponding high-code view loading configuration, loading the program resources, initializing the corresponding high-code view based on the access parameters, mounting the initialized high-code view to a preset view container to generate a high-code target view; and using the low-code target view or the high-code target view as the loading result corresponding to the business access request.

[0032] In this embodiment of the invention, after receiving a business access request, the access address, query fields, and path parameters in the request are parsed to obtain the target access path and access parameters. The target access path is used to determine the business page corresponding to this access, and the access parameters are used to limit the initialization content of the target page. Taking the customer details access request " / customer / detail?id=C1025" as an example, the target access path is " / customer / detail", and the access parameters include the customer identifier C1025. For the access request " / customer / detail / C1025" using path parameters, the fixed path segment " / customer / detail" is used as the target access path, and the last-level path segment C1025 is parsed into access parameters.

[0033] The unified route registration relationship is queried based on the target access path, and a target route node consistent with the target access path is matched. When the unified route registration relationship contains both entry routes and associated routes, matching is first performed based on the complete path; if no corresponding route node exists for the complete path, associated routes are queried level by level according to the path hierarchy. After matching is completed, the view registration item corresponding to the target route node is read, and the view type, view resource description information, and view loading configuration of the target view are obtained from the view registration item. The view loading configuration is consistent with the configuration generated in step S2, and is used to specify the resource acquisition order, page initialization method, and view mounting location.

[0034] Access parameters are written into the corresponding view loading configuration to generate a view loading request for the target view. The view loading request includes at least the target route node identifier, view type, view resource, access parameters, and view container identifier. Access parameters are organized according to the parameter receiving method recorded in the view loading configuration. For example, a low-code customer details view writes the customer identifier C1025 into the query conditions of the page data source, while a high-code device display view writes the device identifier D206 into the initialization parameters of the program module. For parameters not carried in the access request but necessary for target view initialization, they are supplemented based on the parent route parameters of the current route node or the common runtime context; if the corresponding parameters are still not obtained, the current view loading is terminated, and the current view is retained.

[0035] Furthermore, the view loading request is parsed to obtain the view type, view resources, and access parameters corresponding to the target view. When the target view is a low-code view, page metadata is read according to the low-code view loading configuration, and the page layout, component hierarchy, field configuration, and event configuration are parsed to form the page structure. Subsequently, the access parameters are written into the data source initialization conditions, the corresponding business data is loaded, and the page rendering is completed according to the component hierarchy. For example, the customer details page first generates the basic layout and field components, then queries customer information based on the customer identifier C1025, writes the query results into the corresponding fields, and finally generates the low-code target view.

[0036] When the target view is a high-code view, the program module entry point and dependency resource list are read according to the high-code view loading configuration. Runtime libraries, style resources, and the target program module are then loaded according to the dependencies. After the program resources are loaded, access parameters are passed to the module initialization entry point to generate the corresponding high-code view instance. This high-code view instance is then mounted to the preset view container specified in the view loading configuration. For example, after receiving the device identifier D206, the device display program module loads the corresponding device data and 3D model resources, forming a high-code target view within the content container of the business page.

[0037] The generated low-code or high-code target view is used as the loading result corresponding to this business access request, and the correspondence between the loading result and the target route node is recorded to provide a view source for subsequent page combination and route jump. In other embodiments, the business access request is triggered in the form of a hash path, query string, or message event. As long as the target access path and access parameters can be parsed, they all fall within the protection scope of the business access request described in this embodiment.

[0038] Step S4: Combine the loaded low-code view and high-code view in a unified application runtime environment, and enable the high- and low-code views to run collaboratively in the business application based on the unified routing registration relationship.

[0039] Specifically, the loaded low-code and high-code views are combined in a unified application runtime environment, including: obtaining the low-code and high-code target views already loaded in the business application, as well as the view container identifier and page layout position corresponding to each target view; mounting the low-code and high-code target views to the corresponding view containers in the unified application runtime environment according to the view container identifiers; combining the layouts of each view container according to the page layout positions, and associating each view container with a common runtime context in the unified application runtime environment; establishing routing jump relationships between each view container according to the unified routing registration relationship, and generating a converged business application composed of the low-code and high-code target views.

[0040] Furthermore, the collaborative operation of high- and low-code views in business applications is achieved based on a unified routing registration relationship, including: receiving a page jump request corresponding to the current view; determining the next target view and the view loading configuration corresponding to the next target view according to the unified routing registration relationship; obtaining the common runtime context and business status data corresponding to the current view; converting the business status data according to the view type of the next target view and a preset state transition relationship to obtain the initialization data corresponding to the next target view; loading the next target view according to the view loading configuration; and passing the common runtime context and the initialization data to the next target view; and updating the current routing state after the next target view is loaded, while maintaining the continuity of the common runtime context in the business application.

[0041] In this embodiment of the invention, low-code and high-code target views that have been loaded in the business application are obtained, and the view container identifier and page layout position corresponding to each target view are read. The view container identifier is used to determine the mounting area of ​​the target view in the unified application runtime environment, and the page layout position is used to determine the display hierarchy and arrangement position of the corresponding view container in the application page. For example, the low-code target view corresponding to the customer list is mounted in the main content container content-main, and the high-code target view corresponding to the device 3D display is mounted in the auxiliary content container content-side. The former is located in the main area of ​​the page, and the latter is located in the extended area to the right of the main area.

[0042] Based on the view container identifier, each target view is mounted to its corresponding view container in the unified application runtime environment. The low-code target view retains the page structure, component states, and data source connection relationships generated in step S3; the high-code target view retains the view instance and its dependent resources formed after the program module initialization. After the views are mounted, the view containers are combined according to their page layout positions, so that target views corresponding to different resource generation methods enter the same application page framework. The layout combination includes the display area, hierarchy, and switching relationships of the view containers; it is not required that the low-code and high-code target views always be displayed simultaneously. When the corresponding business function is organized using a page jump method, each view container is selectively displayed according to the current routing state; when the corresponding business function is organized using a partitioned display method, each view container is displayed together according to its page layout position.

[0043] Associating each view container with a common runtime context within a unified application runtime environment. This common runtime context includes user identifier, login status, permission information, tenant identifier, language configuration, and theme configuration. The common runtime context is stored using a unified field structure. Each view reads the corresponding information from this common runtime context when it is loaded or activated, avoiding the need for low-code and high-code target views to establish separate login statuses or repeatedly obtain user permissions. Based on a unified routing registration relationship, the routing nodes corresponding to each view container and their jump associations are bound together, forming a converged business application composed of both low-code and high-code target views.

[0044] Furthermore, when the current view generates a page redirection request, the next access path in the page redirection request is parsed, and the next target view and its view loading configuration are determined according to the unified routing registration relationship. Simultaneously, the common runtime context and business status data corresponding to the current view are obtained. The business status data includes the current business object identifier, query conditions, selected records, and page operation position. Based on the view type of the next target view and the preset state transition relationship, the business status data in the current view is converted into the initialization data corresponding to the next target view.

[0045] For example, when navigating from a low-code customer list view to a high-code customer analysis view, the customer identifier (customerId), query time range (dateRange), and selected records (selectedRows) in the low-code view are converted into customerCode, analysisPeriod, and selectedCustomerIds, respectively, which are received by the high-code view. The preset state transition relationship records the source state fields, target initialization fields, and data type conversion methods. State fields that cannot be matched and do not affect the initialization of the target view are not passed; if the required initialization fields of the target view do not have corresponding values, the current view is retained, and the current navigation process is stopped.

[0046] Resource loading is completed according to the view loading configuration corresponding to the next target view, and the common runtime context and initialization data are passed to the next target view. After the next target view completes initialization, the current route state and the display state of the corresponding view container are updated, while the user identifier, login state, and permission information in the common runtime context remain unchanged, thereby realizing continuous navigation and collaborative operation between low-code views and high-code views. In other embodiments, business state data is passed using page caching, session storage, or common state objects, all of which fall within the protection scope of the high-low code view collaborative operation method described in this embodiment.

[0047] like Figure 2As shown, this embodiment takes customer management business application as an example. Low-code views are used for the customer list, customer details, and device list, while high-code views are used for customer analysis and 3D device display. First, the routing path, view type, and resource entry point for each view are registered in the unified routing orchestration page. The customer list corresponds to " / customer / list" and the page metadata `customerList.json`, while customer analysis corresponds to " / customer / analysis" and the program entry point `customerAnalysis / index.js`. Based on the page navigation relationships between the customer list and customer details, customer details and customer analysis, and device list and 3D device display, a unified routing registration relationship is formed, and the corresponding view loading method, initialization parameters, and mounting container are configured for each routing node.

[0048] When a business access request for the customer analytics page is received, the system parses the target access path and access parameters such as customerId. Based on the unified routing registration relationship, it matches the corresponding high-code view registration item for customer analytics, reads the program entry point and dependent resources, loads program resources, initializes the customer analytics view based on the access parameters, and then mounts it to the content-main container. If the target view is a customer list, the system reads the corresponding page metadata, parses the layout, components, and data source configuration, and then renders the page. During the loading process of both types of views, a common runtime context is associated with user identifiers, login status, permission information, tenant identifiers, theme configurations, language configurations, and business status data, enabling continuous navigation and collaborative display between the low-code and high-code views within the same application framework.

[0049] Reference Figure 3 , Figure 3 This is a schematic diagram of the structure of a unified development system that supports dynamic fusion and orchestration of high and low code in an embodiment of the present invention.

[0050] like Figure 3 As shown in the figure, the unified development system supporting dynamic fusion and orchestration of low-code and high-code views proposed in this embodiment of the invention includes: a collection module, used to acquire view configuration data corresponding to each view in the business application, determine the corresponding view type according to the view configuration data, and establish a unified routing registration relationship including low-code views and high-code views; a configuration module, used to determine the view resources corresponding to each view according to the unified routing registration relationship, and generate a view loading configuration corresponding to the view type; a loading module, used to receive business access requests, determine the target view according to the unified routing registration relationship, and load the corresponding low-code view resources or high-code view resources according to the view loading configuration; and a combination module, used to combine the loaded low-code views and high-code views in the unified application runtime environment, and realize the collaborative operation of high-code and low-code views in the business application based on the unified routing registration relationship.

[0051] It is understood that in the description of this specification, references to terms such as "one embodiment," "another embodiment," "other embodiments," or "first embodiment to Nth embodiment," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0052] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0053] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A unified development method supporting dynamic fusion and orchestration of high- and low-code, characterized in that, The method includes the following steps: Obtain view configuration data corresponding to each view in the business application, determine the corresponding view type based on the view configuration data, and establish a unified routing registration relationship that includes low-code views and high-code views; Based on the unified routing registration relationship, the view resources corresponding to each view are determined, and a view loading configuration corresponding to the view type is generated; wherein, After generating the view loading configuration, the dependency library identifiers, dependency versions, and global variable declarations are extracted from the program resources of each high-code view, and the version information of the runtime library corresponding to the page metadata of each low-code view is extracted. Based on the differences in dependency versions and duplicate global variable names between different views, resource conflicts are identified. For each resource conflict, an independent namespace and dependency isolation identifier are written into the corresponding view loading configuration, enabling conflicting program resources to be loaded in different scopes. Specifically, the dependency resolution path corresponding to the conflicting program resource is determined based on the independent namespace and dependency isolation identifier, and the corresponding program resource is loaded based on the dependency resolution path, so that program resources corresponding to different views are resolved and loaded according to their respective dependencies. Upon receiving a service access request, the system determines the target view based on the unified routing registration relationship and loads the corresponding low-code view resource or high-code view resource according to the view loading configuration; wherein, When the target view is a high-code view, the program module entry and dependency resource list are read according to the high-code view loading configuration, and the runtime library, style resources and target program module are loaded according to the dependency relationship. After the program resources are loaded, the access parameters are passed to the module initialization entry, the corresponding high-code view instance is generated, and the high-code view instance is mounted to the preset view container specified by the view loading configuration. The loaded low-code view and high-code view are combined in a unified application runtime environment, and the high- and low-code views in business applications are enabled to run collaboratively based on a unified routing registration relationship; among them, The loaded low-code and high-code views are combined in a unified application runtime environment, including: obtaining the low-code and high-code target views already loaded in the business application, as well as the view container identifier and page layout position corresponding to each target view; mounting the low-code and high-code target views to the corresponding view containers in the unified application runtime environment according to the view container identifier; combining the layouts of each view container according to the page layout position, and associating each view container with a common runtime context in the unified application runtime environment; establishing routing jump relationships between each view container according to the unified routing registration relationship, and generating a converged business application composed of the low-code and high-code target views; The system enables collaborative operation of high- and low-code views in business applications based on a unified routing registration relationship. This includes: receiving a page navigation request corresponding to the current view; determining the next target view and its corresponding view loading configuration based on the unified routing registration relationship; obtaining the common runtime context and business status data corresponding to the current view; converting the business status data according to the view type of the next target view and a preset state transition relationship to obtain initialization data corresponding to the next target view; loading the next target view according to the view loading configuration and passing the common runtime context and initialization data to the next target view; and updating the current routing state after the next target view is loaded, while maintaining the continuity of the common runtime context in the business application.

2. The unified development method supporting dynamic fusion and orchestration of high- and low-code as described in claim 1, characterized in that, Obtain view configuration data corresponding to each view in the business application, and determine the corresponding view type based on the view configuration data, including: Obtain the view identifier, view routing information, and view resource description information corresponding to each view in the business application; The resource generation method for the corresponding view is determined based on the view resource description information; When the view resource description information corresponds to a page generated based on page metadata, the corresponding view is determined to be a low-code view; When the view resource description information corresponds to a page loaded based on program resources, the corresponding view is determined to be a high-code view; The corresponding view registration information is generated based on the view routing information, the view type, and the view resource description information.

3. The unified development method supporting dynamic fusion and orchestration of high- and low-code as described in claim 2, characterized in that, Establish a unified route registration relationship that includes both low-code and high-code views, including: Retrieve the view registration information corresponding to each view; Based on the view routing information in the view registration information, determine the routing node corresponding to each view; Associate the view type and view resource description information of each view with the corresponding route node to form the view registration item for each route node; The view registration items are organized according to the page navigation relationships between each routing node to generate the unified routing registration relationship.

4. The unified development method supporting dynamic fusion and orchestration of high- and low-code as described in claim 3, characterized in that, The view registration items are organized according to the page navigation relationships between each routing node to generate the unified routing registration relationship, including: Obtain the page access paths and redirection relationships between each routing node; The entry route and associated route corresponding to each route node are determined based on the page access path, and the association relationship between different route nodes is established based on the jump association relationship. Bind the view registration items corresponding to each route node to the corresponding ingress route and associated route to generate a unified route registration relationship that includes route nodes, view types, view resource description information and route associations.

5. The unified development method supporting dynamic fusion and orchestration of high- and low-code as described in claim 4, characterized in that, Based on the unified routing registration relationship, the view resources corresponding to each view are determined, and a view loading configuration corresponding to the view type is generated, including: Based on the unified routing registration relationship, obtain the view registration items corresponding to each routing node; The corresponding view resource is determined based on the view resource description information in the view registration item; Match the corresponding resource loading method according to the view type in the view registration item; When the view type is a low-code view, a low-code view loading configuration is generated based on the corresponding page metadata resources; When the view type is a high-code view, a high-code view loading configuration is generated based on the corresponding program resource information; The view loading configuration is generated by associating the low-code view loading configuration or the high-code view loading configuration with the corresponding view registration item.

6. The unified development method supporting dynamic fusion and orchestration of high- and low-code as described in claim 5, characterized in that, Receiving a service access request and determining the target view based on the unified routing registration relationship includes: Parse the business access request to obtain the target access path and access parameters; Match the corresponding target route node in the unified route registration relationship according to the target access path; Based on the view registration item corresponding to the target routing node, determine the view type, view resource description information, and corresponding view loading configuration of the target view; The access parameters are associated with the view loading configuration to generate a view loading request corresponding to the target view.

7. The unified development method supporting dynamic fusion and orchestration of high- and low-code as described in claim 6, characterized in that, Load the corresponding low-code view resource or high-code view resource according to the view loading configuration, including: Parse the view loading request to obtain the view type, view resources, and access parameters corresponding to the target view; When the target view is a low-code view, the page metadata is obtained according to the corresponding low-code view loading configuration, the page metadata is parsed, and the page is initialized and rendered based on the access parameters to generate the low-code target view. When the target view is a high-code view, the program resources are obtained according to the corresponding high-code view loading configuration, the program resources are loaded and the corresponding high-code view is initialized based on the access parameters, the initialized high-code view is mounted to the preset view container, and a high-code target view is generated. The low-code target view or the high-code target view is used as the loading result corresponding to the business access request.

8. A unified development system that supports dynamic fusion and orchestration of high- and low-code, characterized in that, The system is used to execute the unified development method supporting dynamic fusion and orchestration of high and low code as described in any one of claims 1-7, and the system comprises: The acquisition module is used to obtain the view configuration data corresponding to each view in the business application, determine the corresponding view type based on the view configuration data, and establish a unified routing registration relationship that includes low-code views and high-code views. The configuration module is used to determine the view resources corresponding to each view based on the unified routing registration relationship, and to generate the view loading configuration corresponding to the view type; The loading module is used to receive business access requests, determine the target view according to the unified routing registration relationship, and load the corresponding low-code view resources or high-code view resources according to the view loading configuration. The combination module is used to combine the loaded low-code view and high-code view in a unified application runtime environment, and to enable the high- and low-code views to run collaboratively in business applications based on a unified routing registration relationship.

Images