A resource configuration, sharing and loading method and device based on a micro-frontend architecture
By introducing access control and authorization code mechanisms into the micro-frontend architecture, combined with a resource loader, the security threats and cumbersome update operations in micro-frontend resource sharing are solved, achieving flexible, efficient, and secure resource sharing and loading.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- POWERCHINA ZHONGNAN ENG
- Filing Date
- 2026-03-19
- Publication Date
- 2026-07-07
Smart Images
Figure CN121900975B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of micro-frontend resource management technology, and in particular to a method and apparatus for resource configuration, sharing and loading based on a micro-frontend architecture. Background Technology
[0002] With the continuous development of front-end technologies, front-end architecture is also constantly upgrading and evolving. Micro-front-end architecture is a new front-end architecture pattern that breaks down a large front-end application into multiple small, independent sub-applications, each of which can be developed, deployed, and run independently. This architecture pattern can improve the maintainability, scalability, reusability, and testability of front-end applications, and has been widely adopted.
[0003] Front-end resource sharing is a crucial topic because many common front-end resources can be shared in the web development field, including code snippets, stylesheets, images, fonts, configuration data, and more. Currently, industry practice rarely considers resource versioning, security, and copyright issues when sharing front-end resources. Therefore, malicious attackers may intentionally embed malicious code in shared resources, posing a potential security threat to users' websites. Secondly, existing micro-frontend systems require repackaging resources for updates to take effect, a cumbersome process that can negatively impact user experience.
[0004] Therefore, how to make the sharing and use of resources more flexible, efficient and secure has become a technical problem that urgently needs to be solved in this field. Summary of the Invention
[0005] The purpose of this application is to provide a resource configuration, sharing, and loading method and apparatus based on a micro-frontend architecture, which can make resource sharing and use more flexible, efficient, and secure.
[0006] To achieve the above objectives, this application provides the following solution.
[0007] Firstly, this application provides a resource configuration, sharing, and loading method based on a micro-frontend architecture, which includes the following steps:
[0008] Log in to the micro-frontend platform based on user login information.
[0009] Obtain user permissions based on the user login information.
[0010] Based on the user permissions, it is determined whether the user has resource configuration permissions, and a first determination result is obtained.
[0011] If the first determination result is yes, then the user is allowed to define, configure, or update resources.
[0012] If the first judgment result is negative, then only the user is allowed to share resources; the resource sharing includes: resource browsing, resource referencing, resource application, and resource loading.
[0013] Optionally, the resource definition includes: resource type, identifier, name, version, whitelist, and blacklist.
[0014] The resource configuration is used to configure corresponding values according to the resource definition.
[0015] The resource update is used to update resources directly on the micro-frontend platform when updates are needed.
[0016] Optionally, when users share resources, the following steps are included.
[0017] Provides users with all configured resources and allows users to preview the resources.
[0018] After the user obtains the resource attributes, it determines whether the current resource is publicly shared, and obtains the second judgment result.
[0019] If the second judgment result is yes, then copy the resource attributes; based on the copied resource attributes, use a resource loader to load the resource and obtain the loaded resource.
[0020] If the second judgment result is negative, then apply for a resource sharing authorization code, and determine whether the application for the resource sharing authorization code is approved, to obtain the third judgment result.
[0021] If the third judgment result is negative, then resource sharing is rejected.
[0022] If the third judgment result is yes, then copy the resource sharing license code, and copy the resource attributes according to the copied resource sharing license code; use a resource loader to load the resource according to the copied resource attributes and the copied resource sharing license code to obtain the loaded resource.
[0023] Optionally, a resource loader is used to load the resources based on the copied resource attributes and the copied resource sharing license code to obtain the loaded resources, specifically including the following steps.
[0024] Fill the copied resource parameters into the resource loader; the copied resource parameters include: copied resource attributes and copied resource sharing license code.
[0025] Determine if the copied resource sharing license key has a value; obtain the fourth determination result.
[0026] If the fourth judgment result is yes, then set {Resource Identifier: Authorization Code} in the request header.
[0027] If the fourth judgment result is negative, the copied resource parameters are passed to the backend service, and it is determined whether the current resource is publicly shared, thus obtaining the fifth judgment result.
[0028] If the fifth judgment result is negative, then obtain the request header {Resource Identifier: Authorization Code}, and determine whether it is a correct resource sharing authorization code to obtain the sixth judgment result.
[0029] If the sixth judgment result is yes, then determine whether the resource sharing authorization code has expired, and obtain the seventh judgment result.
[0030] If the result of the seventh judgment is negative, a resource link is generated; the micro-frontend platform reads the resource based on the resource link.
[0031] If the result of the seventh judgment is yes, then the resource sharing authorization code has expired.
[0032] If the result of the sixth judgment is negative, then the resource sharing authorization code is incorrect.
[0033] If the fifth judgment result is yes, a resource link is generated, and the micro-frontend platform reads the resource based on the resource link.
[0034] Optionally, the resource loading method of the resource loader is: ResourceLoader(code, version, type, authCode), where code represents the resource identifier, version represents the resource version, type represents the resource type, and authCode represents the resource authorization code.
[0035] Optionally, the resource configuration, sharing, and loading method based on the micro-frontend architecture further includes: allowing all users who are logged into the platform to share resources.
[0036] In a second aspect, this application provides a computer device, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program to implement the resource configuration, sharing, and loading method based on the micro-frontend architecture as described in the first aspect.
[0037] Thirdly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the resource configuration, sharing, and loading method based on the micro-frontend architecture described in any one of the first aspects.
[0038] Fourthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the resource configuration, sharing, and loading method based on the micro-frontend architecture described in any one of the first aspects.
[0039] Based on the specific embodiments provided in this application, the following technical effects are disclosed.
[0040] This application provides a resource configuration, sharing, and loading method and apparatus based on a micro-frontend architecture. The method includes: logging into a micro-frontend platform based on user login information; obtaining user permissions based on the user login information; providing accurate basis for distinguishing permissions for subsequent resource operations, and achieving precise matching of permissions and user identity. Based on the user permissions, it determines whether the user has resource configuration permissions, obtaining a first determination result; if the first determination result is yes, the user is allowed to define, configure, or update resources; if the first determination result is no, the user can only share resources; the resource sharing includes: resource viewing, resource referencing, resource application, and resource loading; it can realize permission-based resource operation, clarify the resource operation boundaries of different users, ensure that authorized users can efficiently complete the full lifecycle management of resources, and meet the needs of dynamic resource control; at the same time, it can realize efficient resource circulation and reuse, ensuring the reasonable resource usage needs of users without configuration permissions. This application, through layered permission control and precise resource operation adaptation, can achieve secure control, efficient configuration, and flexible sharing of resources under the micro-frontend architecture, improving the platform's resource utilization efficiency and overall operational standardization. Attached Figure Description
[0041] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0042] Figure 1 This is a flowchart illustrating a resource configuration, sharing, and loading method based on a micro-frontend architecture, provided as an embodiment of this application.
[0043] Figure 2 This is a schematic diagram illustrating the specific application process of a resource configuration, sharing, and loading method based on a micro-frontend architecture, provided as an embodiment of this application.
[0044] Figure 3 This is a schematic diagram of a resource sharing process provided in an embodiment of this application.
[0045] Figure 4 This is a schematic diagram of a resource loading process provided in an embodiment of this application.
[0046] Figure 5 This is a schematic diagram of the functional modules of a resource configuration, sharing, and loading device based on a micro-frontend architecture, provided in an embodiment of this application.
[0047] Figure 6 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation
[0048] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0049] The purpose of this application is to solve the problem of resource sharing in micro-frontends. It proposes a method and apparatus for resource configuration, sharing, and loading based on a micro-frontend architecture. Resources refer to code snippets, stylesheets, images, fonts, configuration data, etc. To make resource sharing more flexible, efficient, and secure, this application mainly includes three parts.
[0050] (1) Resource configuration strategy based on JWT (JSON Web Token) permission control.
[0051] JWT is an open standard based on JSON used for transmitting declarative authentication information between web applications. To ensure that shared resources are high-quality and secure, access control is implemented for resource configuration. When a user logs into the micro-frontend platform, the system verifies the user's identity and permissions by parsing the token, ensuring that only those with configuration permissions are allowed to configure resources, strictly controlling resource configuration and tracing the responsible parties.
[0052] (2) Resource sharing method based on authorization code.
[0053] To achieve refined control over resources and protect resource copyrights, resource allocation administrators first need to determine which resources are publicly shared and which are not. This application mainly defines the following three categories of resources.
[0054] 1. Public resources: Resources that are accessible to all users or applications and can be used without authorization.
[0055] 2. Authorization code shared resources: Resources that can only be accessed by specific users or applications and require authorization to use.
[0056] 3. Encrypted resources: Resources that can only be accessed under specific conditions, such as specific locations or devices, and require authorization to use.
[0057] For non-publicly shared resources, you need to apply for an authorization code from the configuration administrator before you can use them.
[0058] (3) Resource loading scheme based on loader.
[0059] To ensure secure resource sharing, enable dynamic loading and management of front-end resources, and optimize the performance and user experience of front-end applications, this application provides a loader-based resource loading scheme. When a resource needs to be referenced, simply fill in the resource's basic parameters (and an authorization code for non-publicly shared resources) into the loader to load the resource. This loader-based resource loading scheme not only ensures secure resource sharing but also allows for immediate changes to the resource reference method without requiring adjustments to the code.
[0060] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, this application will be further described in detail below with reference to the accompanying drawings and specific embodiments.
[0061] In one exemplary embodiment, such as Figure 1 As shown, a method for resource configuration, sharing, and loading based on a micro-frontend architecture is provided, which includes the following steps.
[0062] S1: Log in to the micro-frontend platform based on user login information.
[0063] S2: Obtain user permissions based on the user login information.
[0064] S3: Based on the user permissions, determine whether the user has resource configuration permissions, and obtain the first determination result.
[0065] S4: If the first judgment result is yes, then allow the user to define, configure or update resources.
[0066] S5: If the first judgment result is negative, then only users are allowed to share resources; the resource sharing includes: resource viewing, resource referencing, resource application, and resource loading.
[0067] By implementing steps S1 to S5 above, this application can make the sharing and use of resources more flexible, efficient and secure.
[0068] As an optional implementation, the resource definition includes: resource type, identifier, name, version, whitelist, and blacklist.
[0069] The resource configuration is used to configure corresponding values according to the resource definition.
[0070] The resource update is used to update resources directly on the micro-frontend platform when updates are needed.
[0071] As an optional implementation method, such as Figure 3As shown, in step S5, when users share resources, the following steps are included.
[0072] S51: Provides users with all configured resources and allows users to preview the resources.
[0073] S52: After the user obtains the resource attributes, determine whether the current resource is publicly shared, and obtain the second judgment result.
[0074] S53: If the second judgment result is yes, then copy the resource attributes; based on the copied resource attributes, use a resource loader to load the resource and obtain the loaded resource.
[0075] S54: If the second judgment result is negative, then apply for a resource sharing authorization code, and determine whether the resource sharing authorization code is approved to obtain a third judgment result.
[0076] S55: If the result of the third judgment is negative, then resource sharing is rejected.
[0077] S56: If the third judgment result is yes, then copy the resource sharing license code, and copy the resource attributes according to the copied resource sharing license code; use a resource loader to load the resource according to the copied resource attributes and the copied resource sharing license code to obtain the loaded resource.
[0078] As an optional implementation method, such as Figure 4 As shown, in step S56, the resource is loaded using a resource loader based on the copied resource attributes and the copied resource sharing license code to obtain the loaded resource, specifically including the following steps.
[0079] S561: Fill the copied resource parameters into the resource loader; the copied resource parameters include: copied resource attributes and copied resource sharing license code;
[0080] S562: Determine if the copied resource sharing license key has a value; obtain the fourth determination result;
[0081] S563: If the fourth judgment result is yes, then set {Resource Identifier: Authorization Code} in the request header;
[0082] S564: If the fourth judgment result is negative, the copied resource parameters are passed to the backend service, and it is determined whether the current resource is publicly shared, to obtain the fifth judgment result;
[0083] S565: If the fifth judgment result is negative, then obtain the request header {Resource Identifier: Authorization Code}, and determine whether it is a correct resource sharing authorization code to obtain the sixth judgment result;
[0084] S566: If the sixth judgment result is yes, then determine whether the resource sharing authorization code has expired, and obtain the seventh judgment result;
[0085] S567: If the result of the seventh judgment is negative, a resource link is generated; the micro-frontend platform reads the resource according to the resource link;
[0086] S568: If the result of the seventh judgment is yes, then return that the resource sharing authorization code has expired;
[0087] S569: If the result of the sixth judgment is negative, then the resource sharing authorization code is incorrect.
[0088] S5610: If the fifth judgment result is yes, then a resource link is generated, and the micro-frontend platform reads the resource according to the resource link.
[0089] As an optional implementation, the resource loading method of the resource loader is: ResourceLoader(code, version, type, authCode), where code represents the resource identifier, version represents the resource version, type represents the resource type, and authCode represents the resource authorization code.
[0090] As an optional implementation method, the resource configuration, sharing, and loading method based on the micro-frontend architecture further includes: allowing resource sharing for all users who are logged into the platform.
[0091] In practical applications, such as Figure 2 As shown, a method for resource configuration, sharing, and loading based on a micro-frontend architecture is provided, including the following steps.
[0092] (1) Users log in to the micro-frontend platform by entering their account and password.
[0093] (2) The platform determines whether the user has resource configuration permissions.
[0094] (3) If a user has configuration permissions, he / she can define, configure and update resources.
[0095] (4) If a user does not have configuration permissions, he / she can only perform resource sharing operations. It is worth noting that any user who logs into the platform can perform resource sharing.
[0096] like Figure 3 The figure shows a detailed description of step (4), and the main steps are as follows.
[0097] (4.1) Resource search. Users can search for desired resources in the resource library based on attributes such as resource type, identifier, name, and version, and can also preview the resources.
[0098] (4.2) Resource reference. Once a resource is identified, when it needs to be referenced, a resource application is required for non-publicly shared resources.
[0099] (4.3) Resource Request. For resources that are not publicly shared, users need to request permission to use the resource from its owner. After the resource owner approves the request, an authorization code will be returned. It is important to note that this authorization code is the sole credential for the user of the resource.
[0100] (4.4) Resource loading. The self-developed scaffolding provides a resource loading method ResourceLoader(code, version, type, authCode), where code represents the resource identifier, version represents the resource version, type represents the resource type, and authCode represents the resource authorization code. This parameter is not required, but is only required when loading copyrighted resources.
[0101] like Figure 4 The diagram shows a detailed explanation of step (4.4), with the main steps as follows.
[0102] (4.41) Fill in the corresponding resource parameters into the resource loader.
[0103] (4.42) The loader preprocesses the parameters, such as determining whether the resource sharing authorization code has a value. If it does, it sets {resource identifier: authorization code} in the request header.
[0104] (4.43) Obtaining the resource link. The corresponding parameters are passed to the backend via an AJAX request. The backend first determines whether the resource is publicly shared. If so, it directly returns the resource link. Otherwise, it obtains the resource sharing authorization code from the request header and verifies the resource sharing authorization code. Only when the authorization code matches the one issued for the resource is the resource link returned.
[0105] (4.44) Resource loading via resource links. The application loads corresponding resources from the micro-frontend platform service via resource links, achieving resource management for the micro-frontend project and effectively controlling resource access. Furthermore, loading resources via resource links reduces the need to decouple the previously large frontend resource packages. This not only eliminates the need to place all frontend resource packages on a local server, alleviating pressure on the micro-frontend project service, but also solves the problem of needing to repackage resources after resource updates for them to take effect.
[0106] In summary, this application proposes a resource configuration, sharing, and loading method based on a micro-frontend architecture. Resources are defined as entities with attributes such as type, identifier, name, version, whitelist, and blacklist to facilitate subsequent resource sharing. Because frontend resources are updated very frequently, version control issues can easily arise; therefore, a version attribute is added to control resource versions and prevent future version inconsistencies. Furthermore, whitelists and blacklists are set up to protect resource copyright. Resource configuration is subject to access control, allowing only authorized personnel to configure resources. Strict control over resource configuration, tracing back to the responsible party, ensures that shared resources are high-quality and secure. The self-developed resource loading method, ResourceLoader, guarantees that when configured resources are updated, no adjustments to resource references in the code are needed for immediate effect.
[0107] Based on the same inventive concept, this application also provides a resource configuration, sharing, and loading device based on a micro-frontend architecture for implementing the resource configuration, sharing, and loading method based on the micro-frontend architecture described above. The solution provided by this device is similar to the solution described in the above method. Therefore, the specific limitations of one or more embodiments of the resource configuration, sharing, and loading device based on a micro-frontend architecture provided below can be found in the limitations of the resource configuration, sharing, and loading method based on a micro-frontend architecture described above, and will not be repeated here.
[0108] In one exemplary embodiment, such as Figure 5 As shown, a resource configuration, sharing, and loading device based on a micro-frontend architecture is provided, which includes the following modules.
[0109] The login module is used to log in to the micro-frontend platform based on the user's login information.
[0110] The user permission acquisition module is used to acquire user permissions based on the user login information.
[0111] The judgment module is used to determine whether the user has resource configuration permissions based on the user permissions, and obtain a first judgment result.
[0112] The first resource management module is used to allow users to define, configure, or update resources when the first judgment result is yes.
[0113] The second resource management module is used to allow users to share resources only when the first judgment result is negative; the resource sharing includes: resource viewing, resource referencing, resource application, and resource loading.
[0114] In one exemplary embodiment, a computer device is provided, which may be a server or a terminal, and its internal structure diagram may be as follows. Figure 6 As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores user login information. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a resource allocation, sharing, and loading method based on a micro-frontend architecture.
[0115] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0116] In one exemplary embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-described method embodiments.
[0117] In one exemplary embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the above-described method embodiments.
[0118] In one exemplary embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the above-described method embodiments.
[0119] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of the relevant data are carried out in compliance with the relevant data protection laws and policies of the country where the location is located, and with the authorization granted by the owner of the corresponding device.
[0120] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM).
[0121] The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.
[0122] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0123] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A resource configuration, sharing, loading method based on a micro-frontend architecture, characterized in that, The resource configuration, sharing, and loading methods based on the micro-frontend architecture include: Log in to the micro-frontend platform based on user login information; Obtain user permissions based on the user login information; Based on the user permissions, determine whether the user has resource configuration permissions to obtain a first determination result; If the first determination result is yes, then the user is allowed to define, configure or update resources; If the first judgment result is negative, then only resource sharing is allowed; the resource sharing includes: resource viewing, resource referencing, resource application, and resource loading; When users share resources, the following steps are included: Provide users with all configured resources and allow them to preview the resources; After the user obtains the resource attributes, it determines whether the current resource is publicly shared, and obtains the second judgment result; If the second judgment result is yes, then copy the resource attributes; based on the copied resource attributes, use a resource loader to load the resource and obtain the loaded resource; If the second judgment result is negative, then apply for a resource sharing authorization code, and determine whether the resource sharing authorization code application is successful to obtain the third judgment result; If the third judgment result is negative, then resource sharing is rejected; If the third judgment result is yes, then copy the resource sharing license code, and copy the resource attributes according to the copied resource sharing license code; use a resource loader to load the resource according to the copied resource attributes and the copied resource sharing license code to obtain the loaded resource.
2. The resource configuration, sharing and loading method based on the micro-frontend architecture according to claim 1, characterized in that, The resource definition includes: resource type, identifier, name, version, whitelist, and blacklist; The resource configuration is used to configure corresponding values according to the resource definition; The resource update is used to update resources directly on the micro-frontend platform when updates are needed.
3. The method of claim 1, wherein the micro-frontend architecture-based resource configuration, sharing, and loading method is characterized by, Based on the copied resource attributes and the copied resource sharing license key, a resource loader is used to load the resources, resulting in the loaded resources, specifically including: The copied resource parameters are filled into the resource loader; the copied resource parameters include: copied resource attributes and copied resource sharing license code; Determine if the copied resource sharing license key has a value; obtain the fourth result. If the fourth judgment result is yes, then set {Resource Identifier: Authorization Code} in the request header; If the fourth judgment result is negative, the copied resource parameters are passed to the backend service, and it is determined whether the current resource is publicly shared, thus obtaining the fifth judgment result. If the fifth judgment result is negative, then obtain the request header {Resource Identifier: Authorization Code}, and determine whether it is a correct resource sharing authorization code to obtain the sixth judgment result; If the sixth judgment result is yes, then determine whether the resource sharing authorization code has expired, and obtain the seventh judgment result; If the result of the seventh judgment is negative, a resource link is generated; the micro-frontend platform reads the resource based on the resource link. If the result of the seventh judgment is yes, then the resource sharing authorization code has expired. If the result of the sixth judgment is negative, then the resource sharing authorization code is incorrect. If the fifth judgment result is yes, a resource link is generated, and the micro-frontend platform reads the resource based on the resource link.
4. The resource configuration, sharing and loading method based on the micro-frontend architecture according to claim 1, characterized in that, The resource loading method of the resource loader is: ResourceLoader(code, version, type, authCode), where code represents the resource identifier, version represents the resource version, type represents the resource type, and authCode represents the resource authorization code.
5. The resource configuration, sharing, and loading method based on a micro-frontend architecture according to claim 1, characterized in that, The resource configuration, sharing, and loading methods based on the micro-frontend architecture also include: All users who log in to the platform are allowed to share resources.
6. A resource configuration, sharing, and loading device based on a micro-frontend architecture, characterized in that, The resource configuration, sharing, and loading device based on the micro-frontend architecture is used to implement the resource configuration, sharing, and loading method based on the micro-frontend architecture as described in any one of claims 1-5, wherein the resource configuration, sharing, and loading device based on the micro-frontend architecture includes: The login module is used to log in to the micro-frontend platform based on the user's login information; The user permission acquisition module is used to acquire user permissions based on the user login information. The judgment module is used to determine whether the user has resource configuration permissions based on the user permissions, and obtain a first judgment result; The first resource management module is used to allow users to define, configure, or update resources when the first judgment result is yes. The second resource management module is used to allow users to share resources only when the first judgment result is negative; the resource sharing includes: resource viewing, resource referencing, resource application, and resource loading.
7. A computer device, comprising: A memory, a processor, and a computer program stored in the memory and capable of running on the processor, characterized in that the processor executes the computer program to implement the resource configuration, sharing, and loading method based on a micro-frontend architecture as described in any one of claims 1-5.
8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the resource configuration, sharing, and loading method based on the micro-frontend architecture as described in any one of claims 1-5.
9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the resource configuration, sharing, and loading method based on the micro-frontend architecture as described in any one of claims 1-5.