A method, apparatus, device, and storage medium for loading application pages.

Abstract

This invention discloses a method, apparatus, device, and storage medium for loading application pages. The method includes: in response to detecting a page trigger command, acquiring a pre-built application menu tree model; determining the trigger tree node in the application menu tree model corresponding to the page trigger command; and querying the target sub-item node and target page node in the application menu tree model corresponding to the trigger tree node; acquiring the target sub-item identifier mounted on the target sub-item node and the target page identifier mounted on the target page node in the application menu tree model; and loading the target application page in a visual interface based on the target sub-item identifier and the target page identifier. This invention solves the problem that existing micro-frontend architectures require writing sub-item identifiers and page identifiers in the application scheduling code, improving the flexibility and development efficiency of configuring micro-frontend architectures and reducing the maintenance difficulty of frontend applications.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, device, and storage medium for loading application pages. Background Technology

[0002] Micro-frontend is an architecture similar to microservices, which breaks down a large frontend application into multiple independent and flexible sub-projects, each of which can be developed, run, and deployed independently.

[0003] In the existing micro-frontend architecture, sub-projects and sub-project pages developed according to business needs are registered on the base application. The base application responds to user selections triggered by sub-project controls or page controls, and loads the application page based on the sub-project identifier and page identifier corresponding to the selection trigger operation.

[0004] In the process of realizing this invention, at least the following technical problems were found in the prior art:

[0005] The existing micro-frontend architecture is implemented with hard-coded code. When product requirements personnel need to adjust, add or modify sub-projects, both product requirements personnel and developers need to participate in the adaptation, which makes the development efficiency of frontend applications low and difficult to maintain. Summary of the Invention

[0006] This invention provides a method, apparatus, device, and storage medium for loading application pages, in order to solve the problem that existing micro-frontend architectures require sub-project identifiers and page identifiers to be written in the application scheduling code, thereby improving the flexibility and development efficiency of configuring micro-frontend architectures and reducing the maintenance difficulty of frontend applications.

[0007] According to an embodiment of the present invention, a method for loading an application page is provided, the method comprising:

[0008] In response to the detection of a page trigger command, a pre-built application menu tree model is obtained; wherein, the application menu tree model contains at least two tree nodes, and the node types of the tree nodes include sub-item nodes and page nodes;

[0009] Determine the trigger tree node in the application menu tree model that corresponds to the page trigger instruction, and query the target sub-item node and target page node in the application menu tree model that correspond to the trigger tree node;

[0010] Obtain the target sub-item identifier attached to the target sub-item node and the target page identifier attached to the target page node in the application menu tree model;

[0011] Based on the target sub-project identifier and the target page identifier, the target application page is loaded in the visual interface.

[0012] According to another embodiment of the present invention, an application page loading device is provided, the device comprising:

[0013] The application menu tree model acquisition module is used to acquire a pre-built application menu tree model in response to the detection of a page trigger command; wherein, the application menu tree model contains at least two tree nodes, and the node types of the tree nodes include sub-item nodes and page nodes;

[0014] The target page node determination module is used to determine the trigger tree node in the application menu tree model that corresponds to the page trigger instruction, and to query the target sub-item node and target page node in the application menu tree model that correspond to the trigger tree node;

[0015] The target page identifier acquisition module is used to acquire the target sub-item identifier attached to the target sub-item node and the target page identifier attached to the target page node in the application menu tree model;

[0016] The target application page loading module is used to load the target application page in the visual interface based on the target sub-project identifier and the target page identifier.

[0017] According to another embodiment of the present invention, an electronic device is provided, the electronic device comprising:

[0018] At least one processor; and

[0019] A memory communicatively connected to the at least one processor; wherein,

[0020] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the application page loading method according to any embodiment of the present invention.

[0021] According to another embodiment of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, the computer instructions being configured to cause a processor to execute and implement the application page loading method described in any embodiment of the present invention.

[0022] The technical solution of this invention, by mounting sub-project identifiers and page identifiers in the application menu tree model, constructs an application menu tree model containing at least two tree nodes. In response to a detected page trigger command, it queries the trigger tree node corresponding to the page trigger command in the application menu tree model, as well as the target sub-project node and target page node corresponding to the trigger tree node. It obtains the target sub-project identifier mounted on the target sub-project node and the target page identifier mounted on the target page node in the application menu tree model. Based on the target sub-project identifier and target page identifier, it loads the target application page in the visual interface. This solves the problem of existing micro-frontend architectures requiring sub-project identifiers and page identifiers to be written in the application scheduling code. When modifications are needed to sub-projects or pages in the frontend application, only the application menu tree model needs to be modified, without modifying the application scheduling code. This avoids the situation where product requirements personnel and developers are involved in adaptation simultaneously, thereby improving the flexibility and development efficiency of configuring the micro-frontend architecture and reducing the maintenance difficulty of the frontend application.

[0023] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 A flowchart illustrating an application page loading method according to an embodiment of the present invention;

[0026] Figure 2 This is a schematic diagram of an initial menu tree model provided in one embodiment of the present invention;

[0027] Figure 3 This is a schematic diagram of an application menu tree model provided in one embodiment of the present invention;

[0028] Figure 4 This is a schematic diagram of a target application page provided in one embodiment of the present invention;

[0029] Figure 5 A flowchart illustrating another method for loading an application page, as provided in one embodiment of the present invention;

[0030] Figure 6A flowchart illustrating a method for querying target sub-item nodes provided in one embodiment of the present invention;

[0031] Figure 7 A flowchart illustrating another method for loading an application page, as provided in one embodiment of the present invention;

[0032] Figure 8 A flowchart illustrating a method for querying jumper project nodes provided in one embodiment of the present invention;

[0033] Figure 9 This is a schematic diagram of a visual interface provided in one embodiment of the present invention;

[0034] Figure 10 A flowchart illustrating a specific example of an application page loading method provided in an embodiment of the present invention;

[0035] Figure 11 This is a schematic diagram of the structure of an application page loading device provided in one embodiment of the present invention;

[0036] Figure 12 This is a schematic diagram of the structure of an electronic device provided in one embodiment of the present invention. Detailed Implementation

[0037] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0038] It should be noted that the terms "comprising" and "having" and any variations thereof in the specification, claims and accompanying drawings of this invention are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such processes, methods, products or devices.

[0039] Figure 1 This is a flowchart illustrating an application page loading method according to an embodiment of the present invention. This embodiment is applicable to loading application pages in front-end applications based on a micro-front-end architecture. The method can be executed by an application page loading device, which can be implemented in hardware and / or software and can be configured in a terminal device. Figure 1As shown, the method includes:

[0040] S110. In response to the detection of a page trigger command, obtain the pre-built application menu tree model.

[0041] In this embodiment, for example, when a user's selection trigger operation based on a view control displayed in the visual interface is detected, a page trigger instruction is generated based on the view control corresponding to the selection trigger operation. Specifically, the view control can be a sub-item control or a page control.

[0042] In this embodiment, the application menu tree model contains at least two tree nodes, and the node types of the tree nodes include sub-item nodes and page nodes. Specifically, the application menu tree model can be used to represent the nested structure between sub-items and pages, between sub-items, and between pages in the front-end application. The next sub-node corresponding to the current sub-item node in the application menu tree model can be either a next sub-item node or a page node.

[0043] In this embodiment, the application menu tree model is a separate model independent of the application scheduling code. For example, when the base application executes the scheduling process, it can retrieve a pre-built application menu tree model from the storage space. The base application is responsible for the overall layout, sub-project configuration, and scheduling of the entire front-end application, and generally includes common parts of each sub-project, such as the overall application's display framework.

[0044] In one specific embodiment, the method further includes: displaying a pre-built initial menu tree model in a visual interface; wherein the initial menu tree model contains at least two menu nodes; obtaining identification data input by the user based on the initial menu tree model, and configuring each menu node in the initial menu tree model based on the identification data to generate an application menu tree model.

[0045] Specifically, the initial menu tree model can be used to characterize the node architecture of the applied menu tree model. Figure 2 This is a schematic diagram of an initial menu tree model provided in one embodiment of the present invention. Specifically, the initial menu tree model contains at least two levels of menu nodes, such as platform menu nodes, first-level menu nodes, second-level menu nodes, and third-level menu nodes, etc. Typically, the last-level menu node of each branch in the initial menu tree model is a page node.

[0046] In this embodiment, the identification data includes node identifiers corresponding to each menu node in the initial menu tree model. For example, node identifiers may include uppercase letters, numbers, special characters, lowercase letters, Greek letters, etc.

[0047] In one specific embodiment, configuring each menu node in the initial menu tree model based on the identification data to generate an application menu tree model includes: for each menu node in the initial menu tree model, if the identification data contains a node identifier corresponding to the current menu node and the node identifier is a sub-item identifier, attaching the node identifier to the current menu node and using the current menu node as a sub-item node in the application menu tree model; if the identification data contains a node identifier corresponding to the current menu node and the node identifier is a page identifier, attaching the node identifier to the current menu node and using the current menu node as a page node in the application menu tree model.

[0048] Specifically, in the application menu tree model, sub-item nodes are attached with sub-item identifiers, and page nodes are attached with page identifiers.

[0049] Specifically, mounting refers to the operating system attaching a node identifier to a menu node in the initial menu tree model, thus obtaining the applied menu tree model. For example, the node identifier is written to a specified file in the corresponding directory of the menu node in the initial menu tree model.

[0050] Based on the above embodiments, specifically, the node types of tree nodes in the application menu tree model also include group nodes and / or sub-item page nodes. Correspondingly, configuring each menu node in the initial menu tree model based on the identifier data to generate the application menu tree model further includes: if the identifier data does not contain a node identifier corresponding to the current menu node, treating the menu node as a group node in the application menu tree model; and / or, if the identifier data contains a node identifier corresponding to the current menu node, and the node identifier includes a sub-item identifier and a page identifier, attaching the node identifier to the current menu node, and treating the current menu node as a sub-item page node in the application menu tree model.

[0051] In one embodiment, when the node type of the tree node in the applied menu tree model includes group nodes, the identification data contains node identifiers corresponding to some menu nodes in the initial menu tree model. Specifically, group nodes can be used to represent the grouping criteria corresponding to sub-item nodes or page nodes. For example, a group node is an item category, and the sub-item nodes under the group node include daily necessities, clothing, and electronic products, etc.

[0052] In one specific embodiment, the view controls displayed in the visual interface include at least one of sub-item controls, page controls, group controls, and sub-item page controls.

[0053] Figure 3This is a schematic diagram of an application menu tree model provided in one embodiment of the present invention. Specifically, the node types of the tree nodes in the application menu tree model include group nodes, sub-item nodes, page nodes, and sub-item nodes. For example, group node A is data planning, sub-item node B is data warehouse, sub-item node D is data mart, and page node C is financial mart.

[0054] In one specific embodiment, after generating the application menu tree model, the application menu tree model is saved in the storage space for the base application to retrieve during the execution scheduling process.

[0055] S120. Determine the trigger tree node in the application menu tree model that corresponds to the page trigger instruction, and query the target sub-item node and target page node in the application menu tree model that correspond to the trigger tree node.

[0056] Specifically, the visual interface displays view controls corresponding to some or all tree nodes in the application menu tree model. Correspondingly, the trigger tree node is the tree node of the view control in the application menu tree model that corresponds to the page trigger command. In one specific embodiment, the trigger tree node in the application menu tree model is determined based on the control identifier of the view control corresponding to the page trigger command.

[0057] Specifically, the target sub-item node can be either a parent node or a child node of the triggering tree node, and the target page node is a child node of the triggering tree node. In this embodiment, the set of child nodes of the triggering tree node includes the triggering tree node itself.

[0058] In one specific embodiment, querying the target sub-item node and target page node corresponding to the trigger tree node in the application menu tree model includes: querying the tree node set corresponding to the trigger tree node, taking the sub-item node in the tree node set that is closest to the trigger tree node as the target sub-item node, and taking the page node corresponding to the target sub-item node as the target page node. The tree node set includes a child node set and a parent node set.

[0059] by Figure 3 For example, assuming the triggering tree node is group node C, the tree node set corresponding to group node C includes group node A, group node C, sub-item node A, and page node A. In this embodiment, the target sub-item node is sub-item node A, and the target page node is page node A. Assuming the triggering tree node is group node B, the tree node set corresponding to group node B includes group node B, sub-item node E, group node D, page node D, page node E, group node E, and sub-item page node A. In summary, the target sub-item node is sub-item node E, and the target page node is either page node D or page node E.

[0060] S130. Obtain the target sub-item identifier attached to the target sub-item node and the target page identifier attached to the target page node in the application menu tree model.

[0061] Specifically, the target sub-item identifier is obtained from the specified file corresponding to the target sub-item node in the application menu tree model, and the target page identifier is obtained from the specified file corresponding to the target page node in the application menu tree model.

[0062] S140. Based on the target sub-project identifier and the target page identifier, load the target application page in the visual interface.

[0063] Specifically, based on the target sub-project identifier and the target page identifier, a page access link is generated. In response to detecting a change in the page access link, the base application loads the target application page based on the page access link.

[0064] Based on the above embodiments, specifically, loading the target application page in the visualization interface based on the target sub-project identifier and the target page identifier includes: obtaining user permission data based on the target sub-project identifier and the obtained user identifier; generating the target application page based on the target sub-project identifier and the target page identifier, and loading the target application page in the visualization interface based on the user permission data; wherein, the user permission data represents the display permission or operable permission of operable items in the target application page.

[0065] Specifically, the base application sends the target sub-project identifier and user identifier to the corresponding sub-project server, and the sub-project server sends the user permission data corresponding to the user identifier to the base application.

[0066] Specifically, when the current user has low access permissions, some operable items in the target application page loaded in the visual interface may be hidden or unavailable. Figure 4 This is a schematic diagram of a target application page provided according to an embodiment of the present invention. Specifically, Figure 4 Diagrams A and B in the diagram represent target application page A and target application page B, respectively, corresponding to user identifier A and user identifier B. User identifier A has higher user privileges than user identifier B. Compared to target application page A, the "Batch Publish" action option on target application page B is hidden, and the "Publish" action option is unavailable.

[0067] The advantage of this setting is that it increases the user permission functionality of the front-end application, which can improve the security of the front-end application.

[0068] The technical solution of this embodiment, by attaching sub-project identifiers and page identifiers to the application menu tree model, constructs an application menu tree model containing at least two tree nodes. In response to the detection of a page trigger command, it queries the trigger tree node corresponding to the page trigger command in the application menu tree model, as well as the target sub-project node and target page node corresponding to the trigger tree node. It obtains the target sub-project identifier attached to the target sub-project node and the target page identifier attached to the target page node in the application menu tree model. Based on the target sub-project identifier and target page identifier, it loads the target application page in the visual interface. This solves the problem that existing micro-frontend architectures require writing sub-project identifiers and page identifiers in the application scheduling code. When it is necessary to modify the sub-projects or pages in the front-end application, only the application menu tree model needs to be modified, without modifying the application scheduling code. This avoids the situation where product requirements personnel and developers are involved in adaptation at the same time, thereby improving the flexibility and development efficiency of configuring the micro-frontend architecture and reducing the maintenance difficulty of the front-end application.

[0069] Figure 5 This is a flowchart illustrating another application page loading method according to an embodiment of the present invention. This embodiment further optimizes the method for determining the target sub-project node and the target page node in the above embodiments. For example... Figure 5 As shown, the method includes:

[0070] S210. In response to detecting a page trigger command, obtain a pre-built application menu tree model and determine the trigger tree node in the application menu tree model that corresponds to the page trigger command.

[0071] S220. Based on the application menu tree model, query the preset sub-node set corresponding to the trigger tree node.

[0072] In this embodiment, the preset subsystem node set includes the trigger tree node and the subsystem nodes in the subsystem branches of the preset subsystem branch level corresponding to the trigger tree node.

[0073] Specifically, in the application menu tree model, the number of sub-branches corresponding to the trigger tree node may be one or more, and each sub-branch corresponds to a different sub-branch level. Figure 3 For example, if the triggering tree node is group node C, then the number of sub-branches corresponding to group node C is one; if the triggering tree node is group node A, then the number of sub-branches corresponding to group node A is three.

[0074] In one specific embodiment, in the application menu tree model, based on a top-down or bottom-up principle, the sub-branch levels corresponding to each sub-branch of the trigger tree node are determined. Figure 3For example, assuming the trigger tree node is group node A, based on the top-down principle, the sub-branch level corresponding to the sub-branch "Group node C - Sub-project node A - Page node A" is the first sub-branch level, the sub-branch level corresponding to the sub-project node B - Sub-project node C - Page node B is the second sub-branch level, and the sub-branch level corresponding to the sub-project node D - Page node C is the third sub-branch level. For instance, the levels of the first, second, and third sub-branch levels increase or decrease sequentially.

[0075] In this embodiment, for example, the preset sub-branch level can be the first sub-branch level, the second sub-branch level, or the third sub-branch level; the preset sub-branch level is not limited here. In a specific embodiment, the preset sub-branch level is the highest-level sub-branch level. For example, when the levels of the first, second, and third sub-branch levels decrease sequentially, the preset sub-branch level is the first sub-branch level.

[0076] S230. If the preset subsystem node set contains subproject nodes, the last-level subproject node in the preset subsystem node set shall be taken as the target subproject node.

[0077] In one embodiment, when the preset sub-node set contains one sub-item node, the last-level sub-item node in the preset sub-node set is that sub-item node. In another embodiment, when the preset sub-node set contains multiple sub-item nodes, the last-level sub-item node in the preset sub-node set is the sub-item node in the preset sub-node set that is furthest from the trigger tree node.

[0078] by Figure 3 For example, assuming the trigger tree node is group node C, the preset sub-node set corresponding to group node C includes group node C, sub-item node A, and page node A. In this embodiment, the target sub-item node is sub-item node A. Assuming the trigger tree node is group node A, and the preset sub-branch level is the second sub-branch level, the preset sub-node set corresponding to group node A includes group node A, sub-item node B, sub-item node C, and page node B. In this embodiment, the target sub-item node is sub-item node C.

[0079] S240. Use the page node of the preset page level corresponding to the target sub-project node as the target page node.

[0080] Specifically, the target sub-project node may correspond to one or more page nodes, each corresponding to a different page level. Figure 3For example, when the target sub-project node is sub-project node A, the page nodes corresponding to sub-project node A include page node A. When the target sub-project node is sub-project node E, the page nodes corresponding to sub-project node E include page node D and page node E.

[0081] In one specific embodiment, in the application menu tree model, the page level corresponding to each page node corresponding to the target sub-item node is determined based on a top-down or bottom-up principle. Figure 3 For example, when the target sub-project node is sub-project node E, based on the top-down principle, the page level of page node D corresponding to sub-project node E is the first page level, and the page level of page node E corresponding to sub-project node E is the second page level. For instance, the first page level and the second page level may increase or decrease sequentially.

[0082] In this embodiment, for example, the preset page level can be a first page level, a second page level, or a third page level, etc., and the preset page level is not limited here. In a specific embodiment, the preset page level is the highest page level. For example, when the levels of the first page level, the second page level, and the third page level decrease sequentially, the preset page level is the first page level.

[0083] by Figure 3 For example, assuming the trigger tree node is group node B, the preset sub-branch level is the first sub-branch level, and the preset page level is the first page level, then the preset sub-node set corresponding to group node B includes group node B, sub-item node E, group node D, page node D, and page node E. In this implementation, the target sub-item node is sub-item node E, and the target page node is page node D.

[0084] Based on the above embodiments, specifically, the node type of the tree node also includes a sub-item page node, which carries a sub-item identifier and a page identifier. Correspondingly, querying the target sub-item node and target page node corresponding to the triggering tree node in the application menu tree model also includes: when the preset sub-system node set contains sub-item page nodes, the sub-item page nodes are respectively used as target sub-item nodes and target page nodes.

[0085] by Figure 3 For example, assuming the trigger tree node is group node E, the preset sub-node set corresponding to group node E includes group node E and sub-item page node A. In this embodiment, both the target sub-item node and the target page node are sub-item page node A.

[0086] Based on the above embodiments, specifically, querying the target sub-item node and target page node corresponding to the trigger tree node in the application menu tree model further includes: when the preset sub-node set does not contain sub-item nodes, taking the page node of the preset page level in the preset sub-node set as the target page node; querying the parent node set corresponding to the trigger tree node based on the application menu tree model; wherein, the parent node set contains the parent nodes in the parent branch corresponding to the trigger tree node; and taking the last-level sub-item node in the parent node set as the target sub-item node.

[0087] Specifically, the preset set of child nodes corresponding to the triggering tree node may not necessarily contain child item nodes, but it must contain page nodes. Figure 3 For example, assuming the trigger tree node is group node D, the preset sub-node set corresponding to group node D does not contain sub-item nodes, but it does contain page node D and page node E. Similarly, assuming the trigger tree node is page node A, the preset sub-node set corresponding to page node A does not contain sub-item nodes, but it does contain page node A.

[0088] Specifically, in the application menu tree model, the number of parent branches corresponding to the trigger tree node is one.

[0089] In one embodiment, when the parent node set contains a child item node, the last-level child item node in the parent node set is that child item node. In another embodiment, when the parent node set contains multiple child item nodes, the last-level child item node in the parent node set is the child item node in the parent node set that is closest to the trigger tree node.

[0090] by Figure 3 For example, assuming the triggering tree node is page node B, the parent node set corresponding to page node B includes group node A, sub-item node B, and sub-item node C. In this embodiment, the target sub-item node is sub-item node C.

[0091] The advantage of this setup is that if only the preset set of child nodes corresponding to the trigger tree node can be queried, it can easily lead to the unavailability of view controls corresponding to some tree nodes in the application menu tree model. This embodiment improves the query scheme so that regardless of the location of the trigger tree node in the application menu tree model, the corresponding target sub-item node and target page node can be queried, thereby further improving the flexibility of loading application pages and broadening the applicable scenarios.

[0092] Figure 6This is a flowchart illustrating a method for querying a target sub-item node according to an embodiment of the present invention. Specifically, in response to detecting a page trigger command, the method queries the application menu tree model for the trigger tree node corresponding to the page trigger command, and queries the application menu tree model for a preset set of sub-nodes corresponding to the trigger tree node. It determines whether a sub-item node exists in the preset set of sub-nodes. If so, the last-level sub-item node in the preset set of sub-nodes is taken as the target sub-item node, and the target page node corresponding to the target sub-item node is determined. If not, it continues to determine whether a sub-item page node exists in the preset set of sub-nodes. If so, the sub-item page node is taken as both the target sub-item node and the target page node. If not, based on the preset set of sub-nodes, the target page node is determined, and the application menu tree model is queried for the parent node set corresponding to the trigger tree node. The last-level sub-item node in the parent node set is taken as the target sub-item node.

[0093] S250. Obtain the target sub-item identifier attached to the target sub-item node and the target page identifier attached to the target page node in the application menu tree model.

[0094] S260. Based on the target sub-project identifier and the target page identifier, load the target application page in the visual interface.

[0095] The technical solution of this embodiment, based on the application menu tree model, queries the preset sub-node set corresponding to the trigger tree node. When the preset sub-node set contains sub-item nodes, the last-level sub-item node in the preset sub-node set is taken as the target sub-item node, and the page node of the preset page level corresponding to the target sub-item node is taken as the target page node. This solves the query problem of target sub-item nodes and target page nodes, improves the accuracy and query efficiency of target sub-item nodes and target page nodes, and thus improves the loading efficiency of application pages.

[0096] Figure 7 This is a flowchart illustrating another application page loading method provided in one embodiment of the present invention. This embodiment further extends the application page loading method. Figure 7 As shown, the method includes:

[0097] S310. In response to the detection of a page trigger command, obtain the pre-built application menu tree model.

[0098] S320. Determine the trigger tree node in the application menu tree model that corresponds to the page trigger instruction, and query the target sub-item node and target page node in the application menu tree model that correspond to the trigger tree node.

[0099] S330. Obtain the target sub-item identifier attached to the target sub-item node and the target page identifier attached to the target page node in the application menu tree model.

[0100] S340. Based on the target sub-project identifier and the target page identifier, load the target application page in the visual interface.

[0101] S350, In response to detecting a page jump instruction, obtain the jump item identifier and the jump page identifier from the page access link corresponding to the page jump instruction.

[0102] In one specific embodiment, in response to detecting a page access link change instruction, a page jump instruction is generated based on the page access link. For example, when a user enters a page refresh operation, the page access link in the address bar is re-entered, generating a page access link change instruction. Alternatively, when a user enters a new page access link in the address bar, a page access link change instruction is generated in response to detecting a link access operation. Or, when a user clicks on a page control in the target application page, a page access link change instruction is generated based on the page access link corresponding to that page control.

[0103] S360: Based on the application menu tree model, query the jump rotor project node corresponding to the jump rotor project identifier and the jump page node corresponding to the jump page identifier.

[0104] Specifically, the jump rotor project node and the jump page node belong to the same branch. Figure 3 For example, sub-project node A and page node A belong to the same branch, while sub-project node A and page node B belong to different branches.

[0105] In one specific embodiment, based on the application menu tree model, querying the jump rotor project node corresponding to the jump rotor project identifier and the jump page node corresponding to the jump page identifier includes: obtaining the current level branch based on the branch level order in the application menu tree model; if there is a jump rotor project node corresponding to the jump rotor project identifier in the current level branch, querying the jump page node corresponding to the jump page identifier in the current level branch.

[0106] Specifically, based on either a top-down or bottom-up approach, the branch level corresponding to each branch in the application menu tree model is determined. Figure 3 For example, when adopting the top-down principle, the branch "Group Node A - Group Node C - Sub-project Node A and Page Node A" is the first branch level, the branch "Group Node A - Sub-project Node B - Sub-project Node C - Page Node B" is the second branch level, the branch "Group Node A - Sub-project Node D - Page Node C" is the third branch level, and so on.

[0107] In one specific embodiment, based on the application menu tree model, querying the jump rotor project node corresponding to the jump rotor project identifier and the jump page node corresponding to the jump page identifier further includes: if there is no jump rotor project node corresponding to the jump rotor project identifier in the current level branch, or if there is no jump page node corresponding to the jump page identifier in the current level branch, repeatedly executing the step of obtaining the current level branch based on the branch level order in the application menu tree model, until there is a jump page node corresponding to the jump page identifier in the current level branch.

[0108] Figure 8 This is a flowchart illustrating a method for querying jump item nodes according to an embodiment of the present invention. Specifically, in response to detecting a page jump instruction, the jump item identifier and the jump page identifier in the page access link corresponding to the page jump instruction are obtained. Based on the branch level order in the application menu tree model, the current level branch (e.g., the first level branch) is obtained. It is determined whether there is a jump item node corresponding to the jump item identifier in the current level branch. If so, it is further determined whether there is a jump page node corresponding to the jump page identifier in the current level branch. If so, the jump item node and jump page node in the current level branch are determined. If there is no jump item node corresponding to the jump item identifier in the current level branch, or if there is no jump page node corresponding to the jump page identifier in the current level branch, the next level branch is obtained based on the branch level order in the application menu tree model. The next level branch is used as the current level branch, and the above process continues until it is detected that the current level branch simultaneously contains both a jump item node corresponding to the jump item identifier and a jump page node corresponding to the jump page identifier.

[0109] In complex micro-frontend architectures, the same sub-project node identifier may be attached to multiple nodes in the application menu tree model. In other words, multiple sub-project nodes in the application menu tree model may have the same sub-project node identifier. Therefore, there might be situations where the current level branch has a jump sub-project node but no jump page node. In such cases, it's necessary to continue traversing the application menu tree model until the current level branch contains both a jump sub-project node corresponding to the jump sub-project identifier and a jump page node corresponding to the jump page identifier.

[0110] S370. Based on the application menu tree model, obtain the parent node model corresponding to the jump item node and jump page node.

[0111] In this embodiment, the parent node model includes at least one parent node, and each parent node includes at least one target parent node corresponding to the jump item node and the jump page node, as well as sibling nodes corresponding to each target parent node.

[0112] by Figure 3 For example, assuming the jump item node is sub-item node C and the jump page node is page node B, the parent node model is a partial tree model in the application menu tree model consisting of group node A, group node C, sub-item node B, and sub-item node D. Among them, group node A and sub-item node B are the target parent nodes, group node B is the sibling node corresponding to group node A, and group node C and sub-item node D are the sibling nodes corresponding to sub-item node B.

[0113] S380. Based on the parent node model, display each parent node in the visualization interface, and mark and display each target parent node in the parent node model.

[0114] In one specific embodiment, the visualization interface includes a first display area corresponding to the target application page and a second display area corresponding to the parent node model.

[0115] In one specific embodiment, based on the page access link corresponding to the page jump instruction, the target application page is loaded in the first display area of ​​the visualization interface, and each parent node is displayed in the second display area of ​​the visualization interface. Figure 9 This is a schematic diagram of a visual interface provided in one embodiment of the present invention. Specifically, the visual interface includes a first display area and a second display area, wherein the second display area includes a menu sidebar 1 and a menu sidebar 2. Taking the above example, menu sidebar 1 displays the view controls corresponding to group node A and group node B respectively, and menu sidebar 2 displays the view controls corresponding to group node C, sub-item node B, and sub-item node D. Group node A and sub-item node B can be highlighted in menu sidebar 1 and menu sidebar 2 respectively to reflect the nested structure of jump sub-item nodes and jump page nodes in the applied menu tree model.

[0116] Figure 10 This is a flowchart illustrating a specific example of an application page loading method provided in one embodiment of the present invention. Specifically, this embodiment includes an application menu tree model configuration process and a base scheduling process. In the model configuration process, an initial menu tree model pre-built by the user is displayed in a visual interface. Identification data input by the user based on the initial menu tree model is obtained, and node identifiers in the identification data are mounted to the initial menu tree model to obtain the application menu tree model. Exemplarily, the application menu tree model can be output to the base application for the base application to execute the scheduling process.

[0117] Specifically, the base scheduling process includes a control click process and a page navigation process. In the control click process, in response to a detected page trigger command, the system queries the application menu tree model for the trigger tree node corresponding to the page trigger command, and also queries the application menu tree model for the preset sub-node set corresponding to the trigger tree node. It determines whether a sub-item node exists in the preset sub-node set. If so, the last-level sub-item node in the preset sub-node set is taken as the target sub-item node, and the target page node corresponding to the target sub-item node is determined. If not, it continues to determine whether a sub-item page node exists in the preset sub-node set. If so, the sub-item page node is taken as both the target sub-item node and the target page node. If not, based on the preset sub-node set, the target page node is determined, and the application menu tree model queries the parent node set corresponding to the trigger tree node, taking the last-level sub-item node in the parent node set as the target sub-item node. Obtain the target sub-item identifier attached to the target sub-item node and the target page identifier attached to the target page node in the application menu tree model. Based on the target sub-item identifier and the target page identifier, load the target application page in the first display area of ​​the visualization interface.

[0118] In the page navigation process, in response to the detection of a page navigation command, the jump item identifier and the navigation page identifier in the page access link corresponding to the page navigation command are obtained. Based on the branch level order in the application menu tree model, the current level branch (e.g., the first level branch) is obtained. It is determined whether there is a jump item node corresponding to the jump item identifier in the current level branch. If so, it is further determined whether there is a navigation page node corresponding to the navigation page identifier in the current level branch. If so, the jump item node and navigation page node in the current level branch are determined. If there is no jump item node corresponding to the jump item identifier in the current level branch, or if there is no navigation page node corresponding to the navigation page identifier in the current level branch, the next level branch is obtained based on the branch level order in the application menu tree model. The next level branch is used as the current level branch, and the above process continues until it is detected that the current level branch contains both a jump item node corresponding to the jump item identifier and a navigation page node corresponding to the navigation page identifier. Based on the application menu tree model, obtain the parent node model corresponding to the jump project node and jump page node. Based on the parent node model, display each parent node in the second display area of ​​the visualization interface, and mark and display each target parent node in the parent node model.

[0119] The technical solution of this embodiment, in response to the detection of a page jump instruction, obtains the jump item identifier and jump page identifier in the page access link corresponding to the page jump instruction. Based on the application menu tree model, it queries the jump item node corresponding to the jump item identifier and the jump page node corresponding to the jump page identifier. Based on the application menu tree model, it obtains the parent node model corresponding to the jump item node and the jump page node. Based on the parent node model, it displays each parent node in the visualization interface and marks each target parent node in the parent node model. This solves the problem of displaying parent nodes in page jump scenarios, broadens the applicable scenarios for loading application pages, and ensures the consistency of the nested structure between the jump page in the first display area and the view control in the second display area in the complex micro-frontend architecture.

[0120] Figure 11 This is a schematic diagram of the structure of an application page loading device provided in one embodiment of the present invention. Figure 11 As shown, the device includes: an application menu tree model acquisition module 410, a target page node determination module 420, a target page identifier acquisition module 430, and a target application page loading module 440.

[0121] The application menu tree model acquisition module 410 is used to acquire a pre-built application menu tree model in response to the detection of a page trigger command; wherein the application menu tree model contains at least two tree nodes, and the node types of the tree nodes include sub-item nodes and page nodes.

[0122] The target page node determination module 420 is used to determine the trigger tree node in the application menu tree model that corresponds to the page trigger instruction, and to query the target sub-item node and target page node in the application menu tree model that correspond to the trigger tree node.

[0123] The target page identifier acquisition module 430 is used to acquire the target sub-item identifier attached to the target sub-item node and the target page identifier attached to the target page node in the application menu tree model.

[0124] The target application page loading module 440 is used to load the target application page in the visual interface based on the target sub-project identifier and the target page identifier.

[0125] The technical solution of this embodiment, by attaching sub-project identifiers and page identifiers to the application menu tree model, constructs an application menu tree model containing at least two tree nodes. In response to the detection of a page trigger command, it queries the trigger tree node corresponding to the page trigger command in the application menu tree model, as well as the target sub-project node and target page node corresponding to the trigger tree node. It obtains the target sub-project identifier attached to the target sub-project node and the target page identifier attached to the target page node in the application menu tree model. Based on the target sub-project identifier and target page identifier, it loads the target application page in the visual interface. This solves the problem that existing micro-frontend architectures require writing sub-project identifiers and page identifiers in the application scheduling code. When it is necessary to modify the sub-projects or pages in the front-end application, only the application menu tree model needs to be modified, without modifying the application scheduling code. This avoids the situation where product requirements personnel and developers are involved in adaptation at the same time, thereby improving the flexibility and development efficiency of configuring the micro-frontend architecture and reducing the maintenance difficulty of the front-end application.

[0126] Based on the above embodiments, specifically, the device further includes:

[0127] The application menu tree model configuration module is used to display a pre-built initial menu tree model in the visual interface; wherein the initial menu tree model contains at least two menu nodes;

[0128] Obtain the identifier data input by the user based on the initial menu tree model, and configure each menu node in the initial menu tree model based on the identifier data to generate the application menu tree model.

[0129] Based on the above embodiments, specifically, the application menu tree model configuration module includes:

[0130] The sub-item node configuration unit is used to attach the node identifier to the current menu node and set the current menu node as a sub-item node in the application menu tree model for each menu node in the initial menu tree model, provided that the identifier data contains a node identifier corresponding to the current menu node and the node identifier is a sub-item identifier.

[0131] The page node configuration unit is used to attach the node identifier to the current menu node and use the current menu node as a page node in the application menu tree model when the identifier data contains a node identifier corresponding to the current menu node and the node identifier is a page identifier.

[0132] Based on the above embodiments, specifically, the node types of tree nodes also include group nodes and / or sub-item page nodes. Correspondingly, the application menu tree model configuration module also includes:

[0133] A grouping node configuration unit is used to designate a menu node as a grouping node in the applied menu tree model when the identifier data does not contain a node identifier corresponding to the current menu node; and / or,

[0134] The sub-item page node configuration unit is used to attach the node identifier to the current menu node when the identifier data contains the node identifier corresponding to the current menu node, and the node identifier includes both the sub-item identifier and the page identifier, and to use the current menu node as the sub-item page node in the application menu tree model.

[0135] Based on the above embodiments, specifically, the target page node determination module 420 includes:

[0136] The preset sub-node set query unit is used to query the preset sub-node set corresponding to the trigger tree node based on the application menu tree model; wherein, the preset sub-node set includes the trigger tree node and the sub-nodes in the sub-branch of the preset sub-branch level corresponding to the trigger tree node;

[0137] The first target page node determination unit is used to determine the last level of the sub-item node in the preset sub-item node set as the target sub-item node, and the page node of the preset page level corresponding to the target sub-item node as the target page node, when the preset sub-item node set contains sub-item nodes.

[0138] Based on the above embodiments, specifically, the target page node determination module 420 further includes:

[0139] The second target page node determination unit is used to determine the page node of the preset page level in the preset subsystem node set as the target page node when the preset subsystem node set does not contain sub-item nodes.

[0140] Based on the application menu tree model, query the set of parent nodes corresponding to the trigger tree node; where the set of parent nodes contains the parent nodes in the parent branch corresponding to the trigger tree node;

[0141] The last-level child node in the parent node set is taken as the target child node.

[0142] Based on the above embodiments, specifically, the node type of the tree node also includes a sub-item page node, which carries a sub-item identifier and a page identifier. Correspondingly, the target page node determination module 420 also includes:

[0143] The third target page node determination unit is used to determine the sub-project page nodes as target sub-project nodes and target page nodes respectively when the preset sub-system node set contains sub-project page nodes.

[0144] Based on the above embodiments, specifically, the target application page loading module 440 is used for:

[0145] Based on the target sub-project identifier and the obtained user identifier, obtain user permission data;

[0146] Based on the target sub-project identifier and the target page identifier, a target application page is generated, and based on user permission data, the target application page is loaded in the visualization interface; wherein, the user permission data represents the display permission or operability permission of operable items in the target application page.

[0147] Based on the above embodiments, specifically, the device further includes:

[0148] The jump page identifier query module is used to retrieve the jump sub-project identifier and jump page identifier from the page access link corresponding to the page jump instruction after loading the target application page in the visual interface based on the target sub-project identifier and the target page identifier, in response to the detection of the page jump instruction.

[0149] The jump page node determination module is used to query the jump rotor project node corresponding to the jump rotor project identifier and the jump page node corresponding to the jump page identifier based on the application menu tree model.

[0150] The parent node model determination module is used to obtain the parent node model corresponding to the jump item node and the jump page node based on the application menu tree model; wherein, the parent node model contains at least one parent node, and each parent node includes at least one target parent node corresponding to the jump item node and the jump page node, as well as sibling nodes corresponding to each target parent node respectively.

[0151] The parent node model display module is used to display each parent node in the visualization interface based on the parent node model, and to mark and display each target parent node in the parent node model.

[0152] Based on the above embodiments, specifically, the jump page node determination module is used for:

[0153] Based on the branch level order in the application menu tree model, obtain the current level branch;

[0154] If a jump rotor project node corresponding to the jump rotor project identifier exists in the current level branch, query the jump page node corresponding to the jump page identifier in the current level branch.

[0155] Based on the above embodiments, specifically, the jump page node determination module is used for:

[0156] If there is no jump rotor item node corresponding to the jump rotor item identifier in the current level branch, or if there is no jump page node corresponding to the jump page identifier in the current level branch, repeat the step of obtaining the current level branch based on the branch level order in the application menu tree model until there is a jump page node corresponding to the jump page identifier in the current level branch.

[0157] The application page loading device provided in this embodiment of the invention can execute the application page loading method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0158] Figure 12 This is a schematic diagram of an electronic device provided according to one embodiment of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0159] like Figure 12 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0160] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0161] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the application page loading method.

[0162] In some embodiments, the application page loading method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the application page loading method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the application page loading method by any other suitable means (e.g., by means of firmware).

[0163] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0164] One embodiment of the present invention also provides a computer-readable storage medium storing computer instructions for causing a processor to execute an application page loading method, the method comprising:

[0165] In response to the detection of a page trigger command, a pre-built application menu tree model is obtained; wherein, the application menu tree model contains at least two tree nodes, and the node types of the tree nodes include sub-item nodes and page nodes;

[0166] Identify the trigger tree node in the application menu tree model that corresponds to the page trigger instruction, and query the target sub-item node and target page node in the application menu tree model that correspond to the trigger tree node;

[0167] Obtain the target sub-item identifier attached to the target sub-item node and the target page identifier attached to the target page node in the application menu tree model;

[0168] Based on the target sub-project identifier and the target page identifier, load the target application page in the visual interface.

[0169] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0170] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0171] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0172] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0173] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0174] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for loading an application page, characterized in that, include: In response to the detection of a page trigger command, a pre-built application menu tree model is obtained; wherein, the application menu tree model contains at least two tree nodes, and the node types of the tree nodes include sub-item nodes and page nodes; Determine the trigger tree node in the application menu tree model that corresponds to the page trigger instruction, and query the target sub-item node and target page node in the application menu tree model that correspond to the trigger tree node; Obtain the target sub-item identifier attached to the target sub-item node and the target page identifier attached to the target page node in the application menu tree model; Based on the target sub-project identifier and the target page identifier, load the target application page in the visual interface; Wherein, the target sub-project node is the sub-project node closest to the trigger tree node in the set of parent nodes corresponding to the trigger tree node, or the target sub-project node is a child node of the trigger tree node that has a sub-project identifier attached, and the target page node is a child node of the trigger tree node that has a page identifier attached.

2. The method according to claim 1, characterized in that, The method further includes: A pre-built initial menu tree model is displayed in a visual interface; wherein the initial menu tree model contains at least two menu nodes; Obtain the identifier data input by the user based on the initial menu tree model, and configure each menu node in the initial menu tree model based on the identifier data to generate the application menu tree model.

3. The method according to claim 2, characterized in that, The step of configuring each menu node in the initial menu tree model based on the identification data to generate the application menu tree model includes: For each menu node in the initial menu tree model, if the identification data contains a node identifier corresponding to the current menu node and the node identifier is a sub-item identifier, the node identifier is attached to the current menu node, and the current menu node is used as a sub-item node in the application menu tree model. If the identification data contains a node identifier corresponding to the current menu node and the node identifier is a page identifier, the node identifier is attached to the current menu node, and the current menu node is used as a page node in the application menu tree model.

4. The method according to claim 3, characterized in that, The node types of the tree nodes also include group nodes and / or sub-item page nodes. Correspondingly, configuring each menu node in the initial menu tree model based on the identifier data to generate the application menu tree model further includes: If the identification data does not contain a node identifier corresponding to the current menu node, the menu node will be used as a grouping node in the applied menu tree model; And / or, If the identification data contains a node identifier corresponding to the current menu node, and the node identifier includes a sub-item identifier and a page identifier, then the node identifier is attached to the current menu node, and the current menu node is used as a sub-item page node in the application menu tree model.

5. The method according to claim 1, characterized in that, The querying of the target sub-item node and target page node corresponding to the trigger tree node in the application menu tree model includes: Based on the application menu tree model, query the preset sub-node set corresponding to the trigger tree node; wherein, the preset sub-node set includes the trigger tree node and the sub-nodes in the sub-branch of the preset sub-branch level corresponding to the trigger tree node; If the preset subsystem node set contains subproject nodes, the last-level subproject node in the preset subsystem node set shall be taken as the target subproject node. The page node at the preset page level corresponding to the target sub-project node is taken as the target page node.

6. The method according to claim 5, characterized in that, The querying of the target sub-item node and target page node corresponding to the trigger tree node in the application menu tree model also includes: If the preset sub-system node set does not contain sub-project nodes, the page node of the preset page level in the preset sub-system node set shall be used as the target page node. Based on the application menu tree model, query the set of parent nodes corresponding to the trigger tree node; wherein, the set of parent nodes includes the parent nodes in the parent branch corresponding to the trigger tree node; The last-level child project node in the parent node set is taken as the target child project node.

7. The method according to claim 5, characterized in that, The node type of the tree node also includes sub-item page nodes, which carry sub-item identifiers and page identifiers. Correspondingly, querying the target sub-item node and target page node in the application menu tree model corresponding to the trigger tree node also includes: If the preset sub-system node set contains sub-project page nodes, the sub-project page nodes are respectively used as target sub-project nodes and target page nodes.

8. The method according to any one of claims 1-7, characterized in that, The step of loading the target application page in the visual interface based on the target sub-project identifier and the target page identifier includes: Based on the target sub-project identifier and the obtained user identifier, obtain user permission data; Based on the target sub-project identifier and the target page identifier, a target application page is generated, and based on the user permission data, the target application page is loaded in the visualization interface; wherein, the user permission data represents the display permission or operable permission of operable items in the target application page.

9. The method according to claim 1, characterized in that, After loading the target application page in the visual interface based on the target sub-project identifier and the target page identifier, the method further includes: In response to detecting a page jump instruction, the jump item identifier and the jump page identifier in the page access link corresponding to the page jump instruction are obtained; Based on the application menu tree model, query the jump rotor item node corresponding to the jump rotor item identifier and the jump page node corresponding to the jump page identifier; Based on the application menu tree model, obtain the parent node model corresponding to the jump item node and the jump page node; wherein, the parent node model contains at least one parent node, and each parent node includes at least one target parent node corresponding to the jump item node and the jump page node, as well as sibling nodes corresponding to each target parent node respectively. Based on the parent node model, each parent node is displayed in the visualization interface, and each target parent node in the parent node model is marked and displayed.

10. The method according to claim 9, characterized in that, The step of querying the jump rotor item node corresponding to the jump rotor item identifier and the jump page node corresponding to the jump page identifier based on the application menu tree model includes: Based on the branch level order in the application menu tree model, obtain the current level branch; If a jump rotor project node corresponding to the jump rotor project identifier exists in the current level branch, query the jump page node corresponding to the jump page identifier in the current level branch.

11. The method according to claim 10, characterized in that, The step of querying the jump rotor item node corresponding to the jump rotor item identifier and the jump page node corresponding to the jump page identifier based on the application menu tree model also includes: If there is no jump rotor item node corresponding to the jump rotor item identifier in the current level branch, or if there is no jump page node corresponding to the jump page identifier in the current level branch, repeat the step of obtaining the current level branch based on the branch level order in the application menu tree model until there is a jump page node corresponding to the jump page identifier in the current level branch.

12. A device for loading an application page, characterized in that, include: The application menu tree model acquisition module is used to acquire a pre-built application menu tree model in response to the detection of a page trigger command; wherein, the application menu tree model contains at least two tree nodes, and the node types of the tree nodes include sub-item nodes and page nodes; The target page node determination module is used to determine the trigger tree node in the application menu tree model that corresponds to the page trigger instruction, and to query the target sub-item node and target page node in the application menu tree model that correspond to the trigger tree node; The target page identifier acquisition module is used to acquire the target sub-item identifier attached to the target sub-item node and the target page identifier attached to the target page node in the application menu tree model; The target application page loading module is used to load the target application page in the visual interface based on the target sub-project identifier and the target page identifier; Wherein, the target sub-project node is the sub-project node closest to the trigger tree node in the set of parent nodes corresponding to the trigger tree node, or the target sub-project node is a child node of the trigger tree node that has a sub-project identifier attached, and the target page node is a child node of the trigger tree node that has a page identifier attached.

13. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the application page loading method according to any one of claims 1-11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method for loading an application page according to any one of claims 1-11.

Images