CN115408050A - Micro front terminal application publishing method, device, equipment and storage medium - Google Patents

Abstract

The present disclosure provides a release method, device, and equipment for a micro front end application, that is, a storage medium. The publishing method is applied to the main application of the micro front end, and includes: receiving a loading instruction for the first sub-application; obtaining configuration information of the first sub-application according to the loading instruction; determining the target publishing environment of the first sub-application according to the configuration information; loading The first sub-application is aimed at the application resources of the target release environment; the present disclosure realizes the independent release of micro-frontend sub-applications through the above-mentioned method, and reduces the gray scale cost.

Description

A publishing method, device, equipment, and storage medium for micro-front end applications

technical field

The present disclosure relates to but not limited to the field of computer technology, and in particular relates to a method, device, device, and storage medium for releasing micro-frontend applications.

Background technique

Grayscale release (also known as canary release) refers to a release method that can smoothly transition between black and white. A/B testing can be carried out on it, that is, let some users continue to use product feature A, and some users start to use product feature B. If users have no objection to B, then gradually expand the scope and migrate all users to B. Come. Grayscale publishing can ensure the stability of the overall system, and problems can be found and adjusted at the initial grayscale to ensure their impact.

At present, the sub-applications of the micro-frontend have major upgrades, which need to be released in grayscale, and when the traffic is switched smoothly to ensure stability, all sub-applications of the micro-frontend need to be released in grayscale and need the cooperation of the main application in grayscale, which increases the release work The volume and the cost of gray scale release, and reduce the stability of the system, making the system less flexible.

Contents of the invention

The present disclosure provides a release method, device, equipment and storage medium for micro front end applications, so as to realize the independent release of micro front end applications.

In the first aspect, the present disclosure provides a publishing method for a micro-frontend sub-application. The publishing method is applied to the micro-frontend main application, including: receiving a loading instruction for the first sub-application; and obtaining the configuration of the first sub-application according to the loading instruction information; according to the configuration information, determine the target release environment of the first sub-application; load the application resources of the first sub-application for the target release environment, wherein the target release environment is a gray scale release environment or a production line release environment.

In a possible implementation manner, determining the target publishing environment of the first sub-application according to the configuration information includes: determining whether the grayscale publishing environment is enabled for the first sub-application according to the configuration information; when it is determined that the grayscale publishing environment is enabled, Determine that the target release environment is the grayscale release environment; when it is determined not to enable the grayscale release environment, determine that the target release environment is the production line release environment.

In a possible implementation manner, the configuration information includes: first indication information and resource information of the first sub-application, where the first indication information is used to indicate whether the first sub-application enables a gray scale release environment; the resource information includes: The grayscale resource address corresponding to the grayscale release environment and the production line resource address corresponding to the production line release environment.

In a possible implementation manner, when the first indication information is the first value, the first indication information indicates that the grayscale publishing environment is enabled; or, when the first indication information is the second value, the first indication information indicates that the Enable grayscale publishing environment.

In a possible implementation, the publishing method further includes: acquiring a modification instruction, the modification instruction is used to switch the first indication information from indicating that the grayscale publishing environment is enabled to indicating that the grayscale publishing environment is not enabled; according to the modification instruction, modifying The first instruction message.

In a possible implementation manner, in response to the fact that the target publishing environment is a grayscale publishing environment, loading the application resources of the first sub-application for the target publishing environment includes: obtaining the grayscale resource address corresponding to the grayscale publishing environment, obtaining the grayscale The application resources corresponding to the release environment.

In a possible implementation manner, in response to the fact that the target release environment is the production line release environment, loading the application resources of the first sub-application for the target release environment includes: obtaining the production line resource address corresponding to the production line release environment to obtain the Application resources corresponding to the online publishing environment.

In a possible implementation manner, before receiving the loading instruction for the first sub-application, the issuing method further includes: receiving a configuration instruction for the first sub-application; according to the configuration instruction, in the source configuration file of the first sub-application Configure the environment parameters of the grayscale release environment and/or the environment parameters of the production line release environment in ; edit the configured source configuration file of the first sub-application to obtain the application resources and/or production line releases corresponding to the grayscale release environment Application resources corresponding to the environment.

In a second aspect, the present disclosure provides a publishing device for micro-frontend sub-applications. The publishing device includes: a processing module, configured to receive a loading instruction for the first sub-application; a first processing module, configured to obtain the first sub-application according to the loading instruction. Configuration information of a sub-application; a second processing module, configured to determine the target publishing environment of the first sub-application according to the configuration information; a sending module, used to load application resources of the first sub-application for the target publishing environment, wherein the target publishing environment The environment is grayscale release environment or production line release environment.

In a possible implementation manner, the second processing module is further configured to: determine whether the first sub-application enables the grayscale publishing environment according to the configuration information; when it is determined that the grayscale publishing environment is enabled, determine that the target publishing environment is grayscale Release environment; when it is determined not to enable the grayscale release environment, determine that the target release environment is the production line release environment.

In a possible implementation manner, the configuration information includes: first indication information and resource information of the first sub-application, where the first indication information is used to indicate whether the first sub-application enables a gray scale release environment; the resource information includes: The grayscale resource address corresponding to the grayscale release environment and the production line resource address corresponding to the production line release environment.

In a possible implementation manner, when the first indication information is the first value, the first indication information indicates that the grayscale publishing environment is enabled; or, when the first indication information is the second value, the first indication information indicates that the Enable grayscale publishing environment.

In a possible implementation manner, the first processing module is also used to obtain a modification instruction, and the modification instruction is used to switch the first indication information from indicating that the grayscale publishing environment is enabled to indicating that the grayscale publishing environment is not enabled; the publishing device It also includes: a modification module, configured to modify the first indication information according to the modification instruction.

In a possible implementation manner, in response to the target publishing environment being a grayscale publishing environment, the sending module is further configured to: obtain the application resource corresponding to the grayscale publishing environment by accessing the grayscale resource address corresponding to the grayscale publishing environment.

In a possible implementation manner, in response to the target release environment being the production line release environment, the sending module is further configured to: obtain the application resource corresponding to the production line release environment by accessing the production line resource address corresponding to the production line release environment.

In a possible implementation manner, the processing module is further configured to receive a configuration instruction for the first sub-application; the device further includes: a configuration module configured to configure gray information in the source configuration file of the first sub-application according to the configuration instruction. The environment parameters of the high-level release environment and/or the environment parameters of the production line release environment; the editing module is used to edit the source configuration file of the first sub-application after configuration, and obtain the application resources and/or product corresponding to the gray-scale release environment. Application resources corresponding to the online publishing environment.

In a third aspect, the present disclosure provides an electronic device, which includes: a memory for storing processor-executable instructions; a processor; wherein, the processor is configured to: when executing the executable instructions, to implement the following: The method of the first aspect and any possible implementation thereof.

In a fourth aspect, the present disclosure provides a computer-readable storage medium, which is characterized in that the readable storage medium stores an executable program, wherein, when the executable program is executed by a processor, the first aspect and any possible method of implementation.

The technical solution provided by the present disclosure may include the following beneficial effects:

In this disclosure, according to the configuration information of the first sub-application, the target publishing environment of the first sub-application is determined, and the application resources of the target publishing environment of the first sub-application are loaded, so that the independent publishing of micro-front sub-applications is realized, reducing the gray cost. Furthermore, by deploying the configuration information of the micro-frontend sub-applications, it is determined whether the micro-frontend sub-applications can be released in grayscale, which can control the user's access node, smoothly switch traffic between the grayscale release environment and the production line release environment, and improve the grayscale release flexibility.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not intended to limit the scope of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description serve to explain the principles of the disclosure.

FIG. 1 is a schematic diagram of the first implementation flow of the release method of the micro-front end application in the embodiment of the present disclosure;

FIG. 2 is a schematic diagram of an operation interface of the main application of the micro front end in an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of the second implementation flow of the publishing method of the micro-front terminal application in the embodiment of the present disclosure;

FIG. 4 is a schematic diagram of the third implementation flow of the release method of the micro-front end application in the embodiment of the present disclosure;

FIG. 5 is a schematic diagram of the fourth implementation flow of the release method of the micro-front end application in the embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of a release device for a micro-front end application in an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of an electronic device in an embodiment of the present disclosure.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of devices consistent with aspects of the present disclosure as recited in the appended claims.

Other embodiments of the present disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The present disclosure is intended to cover any modification, use or adaptation of the present disclosure. These modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure. . The specification and examples are to be considered exemplary only, with the true scope and spirit of the disclosure being indicated by the following claims.

In order to illustrate the technical solutions described in the present disclosure, specific examples are used below to illustrate.

Internet products need to be continuously upgraded, but system upgrades are always accompanied by risks, such as the risk of compatibility between old and new versions, the risk of user loss due to changes in user usage habits, and the risk of system downtime. In order to avoid these risks, many Internet products have adopted the strategy of grayscale release. The main idea is to concentrate the impact on one point and then spread it to one surface. When unexpected situations occur, it is easy to roll back and avoid causing large-scale influences.

Before Internet products with new functions or improved technologies are released online, if the new release has a large impact, they will consider dividing part of the user traffic first, so that these users can experience the new Internet products first. The data generated by this part of users continuously optimizes new Internet products, and finally officially releases them online, and then allows all users to use them. This grayscale release method reduces the risk of releasing new functions and achieves smooth release.

However, the traditional gray-scale publishing scheme is only for the main application of the micro-frontend, and cannot be applied to the complex scenarios of the micro-frontend terminal application. A gray-scale release scheme for application gray-scale decoupling between applications.

In order to solve the above problems, the present disclosure provides a micro-frontend sub-application release method, which can be applied to a micro-frontend main application to realize independent release of micro-frontend sub-applications.

To clarify, a micro frontend is a type of design applied to the frontend that allows us to divide it into smaller, independent, semi-independent applications and work together, i.e. a single page frontend The main application) is transformed from a single single application to an application that aggregates multiple small front-end applications (ie, micro front-end sub-applications). Each front-end application can also be developed and deployed independently.

Fig. 1 is a schematic diagram of the first implementation flow of the release method of the micro-front end application in the embodiment of the present disclosure. Referring to Fig. 1, the release method may include:

S101. Receive a loading instruction for a first sub-application.

It can be understood that before the micro-frontend sub-application is released in gray scale or production line, the micro-frontend main application first receives a loading instruction from the user, and the loading instruction is used to instruct to load one of the micro-frontend sub-applications. The application (ie, the first sub-application), that is to say, the first sub-application is a micro-frontier sub-application selected by the user to be loaded.

Exemplarily, FIG. 2 is a schematic diagram of an operation interface of the micro-frontend main application in an embodiment of the present disclosure. Referring to FIG. Navigation menu 201 of the application. In the navigation menu 201 of the micro frontend main application 200 , there are one or more registered sub-applications, and each sub-application corresponds to a control in the navigation menu 201 . Then, the user may click on the "payment" control in the navigation menu 201 to indicate that the user requests to load the "payment" sub-application (ie, the first sub-application).

It should be noted that the interface between the micro-frontend main application and the micro-frontend sub-application is an application programming interface (application programming interface, API), and the micro-frontend main application enters the visual interface 202 of the micro-frontend sub-application through the API. The interface between the micro-frontend main application and the micro-frontend sub-application may also be implemented by other devices that can provide a general programming environment, which is not specifically limited in the embodiments of the present disclosure.

S102. Acquire configuration information of the first sub-application according to the loading instruction.

It can be understood that after receiving a loading instruction directed to the first sub-application from the user, the micro-frontend main application obtains configuration information of the first sub-application from the database of the micro-frontend main application in response to the loading instruction.

Exemplarily, as shown in FIG. 2 , the micro-frontend main application 200 receives the user's click operation on the "payment" control in the navigation menu 201, and in response to the click operation, acquires the "payment" item in the database 203. Configuration information of a sub-application.

In a possible implementation manner, the configuration information of the first sub-application may include: first indication information and resource information of the first sub-application. Wherein, the first indication information may be used to indicate whether the first sub-application enables the gray-scale release environment; the resource information of the first sub-application may include: the gray-scale resource address corresponding to the gray-scale release environment and the production line corresponding to the production line release environment resource address.

It should be noted that the configuration information may include but not limited to first indication information and resource information of the first sub-application.

Exemplarily, assuming that the first sub-application is a payment sub-application, then the configuration information of the payment sub-application may include: whether to enable gray-scale publishing environment: yes (that is, the first indication information, and the first indication information indicates that the payment sub-application The application enables gray-scale publishing environment), sub-application name: payment (that is, version information), sub-application production line address: www-payment.app.com (that is, the product line corresponding to the production line release environment in the resource information of the first sub-application online resource address) and sub-application gray-scale address: www-payment-gray.app.com (that is, the gray-scale resource address corresponding to the gray-scale publishing environment in the resource information of the first sub-application).

In a possible implementation manner, when the first indication information is the first value, the first indication information indicates that the grayscale publishing environment is enabled; or, when the first indication information is the second value, the first indication information indicates that the Enable the grayscale publishing environment.

It can be understood that the first indication information is used to indicate whether the first sub-application enables the gray-scale publishing environment, then correspondingly, the first indication information may be the first value corresponding to indicating that the first sub-application enables the gray-scale publishing environment and the indication The first sub-application does not enable the second value of the gray scale publishing environment.

Exemplarily, the expression form of the first value may be "whether to enable the grayscale publishing environment: yes", and the expression form of the second value may be "whether to enable the grayscale publishing environment: no".

It should be noted that, the expression forms of the first value and the second value of the first indication information may also be in other forms, which are not specifically limited in this embodiment of the present disclosure.

S103. Determine a target publishing environment of the first sub-application according to the configuration information.

It can be understood that after the micro frontend main application obtains the configuration information of the micro frontend sub-application, it can determine the target publishing environment of the first sub-application according to the configuration information.

In a possible implementation manner, the above S103 may include S301 to S303. Specifically, FIG. 3 is a schematic flowchart of the second implementation of the release method of the micro-front terminal application in the embodiment of the present disclosure, as shown in FIG. 3 , when executing S103, execute S301 to S303.

S301. According to the configuration information, determine whether the first sub-application enables a gray-scale publishing environment.

It can be understood that, after obtaining the configuration information of the first sub-application, the main application of the micro frontend determines whether the first sub-application enables the gray-scale publishing environment according to the first indication information in the configuration information.

S302. When it is determined to enable the grayscale publishing environment, determine that the target publishing environment is the grayscale publishing environment.

It can be understood that when the first indication information in the configuration information points to enabling the gray scale publishing environment, at this time, the micro frontend main application can determine that the target publishing environment of the first sub-application is the gray scale publishing environment.

Exemplarily, the micro-frontend main application obtains the configuration information of the payment sub-application, and the first indication information of the payment sub-application is "whether to enable gray-scale publishing environment: yes", then the micro-frontend main application determines that the payment sub-application enables gray-scale publishing surroundings.

S303. When it is determined not to enable the grayscale release environment, determine that the target release environment is the production line release environment.

It can be understood that when the first indication information in the configuration information indicates that the gray scale publishing environment is not enabled, at this time, the micro frontend main application can determine that the target publishing environment of the first sub-application is the production line publishing environment.

Exemplarily, the micro-frontend main application obtains the configuration information of the collection sub-application, and the first indication information of the collection sub-application is "whether to enable gray-scale release environment: No", then the micro-frontend main application determines that the collection sub-application enables production line release surroundings.

S104. Load the application resources of the first sub-application for the target publishing environment.

Among them, the target release environment is the grayscale release environment or the production line release environment.

It can be understood that after the micro frontend main application determines the target publishing environment of the first sub-application according to the configuration information, it can load the application resources of the first sub-application according to the resource information in the configuration information.

In an embodiment, after performing the above S302, in response to the target publishing environment being a grayscale publishing environment, the above S104 may include: obtaining the application resource corresponding to the grayscale publishing environment by accessing the grayscale resource address corresponding to the grayscale publishing environment .

Exemplarily, after the micro-frontend main application determines that the target publishing environment of the payment sub-application is the gray publishing environment, it can obtain the payment by accessing the gray resource address of the payment sub-application, namely www-payment-gray.app.com The application resources of the sub-application's gray scale publishing environment.

In another embodiment, after performing the above S302, in response to the target release environment being the production line release environment, the above S104 may include: obtaining the application corresponding to the production line release environment by accessing the production line resource address corresponding to the production line release environment resource.

Exemplarily, after the micro-frontend main application determines that the target release environment of the collection sub-application is the production line release environment, it can obtain the collection sub-application by accessing the production line resource address of the collection sub-application, namely www-collection.app.com The application resources of the production line release environment.

It should be noted that application resources may include static resources such as pictures, hypertext markup language (hyper text markup language, HTML), cascading style sheets (cascading style sheets, CSS) and Java script (javascript, JS), and static resources may be stored in In a content delivery network (CDN), static resources are loaded through the CDN; application resources can also include dynamic resources such as programs, web pages, and components running on the server side, and the main micro-frontend application can mount dynamic resources on the window On .global, the micro-frontend sub-application loads dynamic resources by directly calling window.global.

It can be understood that the publishing environment of the micro-frontend sub-application can be switched, such as switching from a gray scale publishing environment to a production line publishing environment. Then, when the micro-frontend main application switches the publishing environment of the micro-frontend sub-application, it needs to modify the configuration information of the micro-frontend sub-application.

In a possible implementation manner, the publishing method of the above-mentioned micro-frontier sub-application may further include: obtaining a modification instruction, the modification instruction is used to switch the first indication information from indicating that the gray-scale publishing environment is enabled to indicating that the gray-scale publishing environment is not enabled ; Modify the first indication information according to the modification instruction.

It can be understood that when the micro-frontend main application switches the target publishing environment of the first sub-application from the grayscale publishing environment to the production line publishing environment, the micro-frontend main application obtains modification instructions from the user, and then modifies the first sub-application according to the above modification instructions. The first indication information in the configuration information of the application.

Exemplarily, the micro-frontend main application obtains a modification instruction from the user, and according to the modification instruction, modifies the first instruction information of the payment sub-application, that is, "whether to enable the gray-scale publishing environment: yes", to "whether to enable the gray-scale publishing environment: no".

Before executing the above S101 to S104, the configuration information of the micro frontend sub-application can be deployed in the micro frontend main application, at this time, the steps of S401 to S403 are executed. FIG. 4 is a schematic flowchart of a third implementation of the release method of the micro front end application in the embodiment of the present disclosure. Referring to FIG. 4 , before executing S101 to S104 , execute S401 to S403 .

S401. Receive a configuration instruction for a first sub-application.

It can be understood that when deploying the configuration information of the micro-frontend sub-application, the micro-frontend main application first receives a configuration instruction for the first sub-application.

S402. According to the configuration instruction, configure the environment parameters of the gray scale release environment and/or the environment parameters of the production line release environment in the source configuration file of the first sub-application.

It can be understood that when the first sub-application is to be released in grayscale, the micro frontend main application configures the environment parameters of the grayscale release environment and the production line release environment in the source configuration file of the first sub-application according to the configuration instructions; When a sub-application is only released to the production line, configure the environment parameters of the production line release environment in the source configuration file of the first sub-application.

Exemplarily, when the payment sub-application is to be published in gray scale, the main application of the micro-frontend finds the gray. Configure environment variables, for example: ENV_CONFIG="gray" (i.e. the environment parameters of the gray release environment); at the same time, the micro-frontend main application also finds the prod.env of the payment sub-application in the micro-frontend project root directory /config according to the configuration instructions .js file, configure environment variables, for example: ENV_CONFIG="prod". When the collection sub-application is going to be released to the production line, the micro-frontend main application finds the prod.env.js file of the collection sub-application in the micro-frontend project root directory /config according to the configuration instructions, and configures environment variables, for example: ENV_CONFIG="prod ".

S403. Edit the configured source configuration file of the first sub-application to obtain the application resources corresponding to the gray scale release environment and/or the application resources corresponding to the production line release environment.

It can be understood that after the main micro-frontend application configures the source configuration file of the first sub-application according to the configuration instructions, and then edits the configured source configuration file, the application resources and /or the application resources corresponding to the production line release environment.

Exemplarily, when the micro-frontend main application deploys the configuration information of the payment sub-application, after configuring the environment parameters of the payment sub-application, the micro-frontend main application triggers the micro-frontend program packaging command of the payment sub-application through jenkins, and the micro-program packaging command For "npm run build", generate the gray release environment code and production line release environment code of the payment sub-application. The above code contains the application resources of the payment sub-application.

The above publishing method will be described in detail below using the publishing method of the payment sub-application.

Fig. 5 is a schematic diagram of the fourth implementation flow of the release method of the micro-front terminal application in the embodiment of the present disclosure. Referring to Fig. 5, the above method may include:

S501. The main micro-frontend application receives a configuration instruction for the payment sub-application from a user.

S502. According to the configuration instruction in S501, the micro-frontend main application configures the environment parameters of the payment sub-application's gray scale release environment and production line release environment.

S503, the micro-frontend main application edits the environment parameters in S502, generates grayscale release codes and production line release environment codes of the payment sub-application, and obtains application resources of the grayscale release environment and production line release environment.

S504. Execute the above S503, that is, after deploying the configuration information of the payment sub-application, log in to the micro-frontend main application again, and receive a recording instruction for the payment sub-application from the user.

S505, the micro-frontend main application acquires configuration information of the payment sub-application according to the loading instruction in S504.

S506. According to the configuration information in S505, determine that the target publishing environment of the payment sub-application is the grayscale publishing environment.

S507, the micro-frontend main application loads the application resources of the gray scale publishing environment of the payment sub-application in S503.

S508, the micro frontend main application receives a modification instruction from the user.

S509, the micro frontend main application modifies the first indication information of the payment sub-application from the first value to the second value according to the modification instruction in S508.

S510, log in to the micro-terminal main application again, and load the application resources of the production line publishing environment of the payment sub-application.

So far, the release method of the micro-frontend sub-application has been realized.

In the embodiment of the present disclosure, according to the configuration information of the first sub-application, the target publishing environment of the first sub-application is determined, and the application resources of the target publishing environment of the first sub-application are loaded, realizing the independent publishing of micro-frontier sub-applications, Reduced gray scale cost. Furthermore, by deploying the configuration information of the micro-frontend sub-applications, it is determined whether the micro-frontend sub-applications can be released in grayscale, which can control the user's access node, smoothly switch traffic between the grayscale release environment and the production line release environment, and improve the grayscale release flexibility.

Based on the same inventive concept, an embodiment of the present disclosure also provides a release device for a micro-front end application. The release device can be a chip or a system-on-a-chip in an electronic device, and can also be used in an electronic device to implement one or more of the above. The functional modules of the method described in the embodiment and any possible implementation thereof. The publishing apparatus may realize the functions performed by the electronic device in the foregoing one or more embodiments and any possible implementation manner thereof, and the foregoing functions may be realized by executing corresponding software through hardware. These hardware or software include one or more modules with corresponding functions mentioned above. Fig. 6 is a schematic structural diagram of a release device for a micro-front end application in an embodiment of the present disclosure. Referring to Fig. 6 , the release device 600 for a micro-front end application may include: The loading instruction of the application; the first processing module 602 can be used to obtain the configuration information of the first sub-application according to the loading instruction; the second processing module 603 can be used to determine the target publishing environment of the first sub-application according to the configuration information; The sending module 604 may be configured to load application resources of the first sub-application for a target release environment, where the target release environment is a gray scale release environment or a production line release environment.

In a possible implementation manner, the second processing module 603 may also be configured to: determine whether the first sub-application enables the grayscale publishing environment according to the configuration information; when it is determined that the grayscale publishing environment is enabled, determine that the target publishing environment is Grayscale release environment; when it is determined not to enable the grayscale release environment, determine that the target release environment is the production line release environment.

In a possible implementation manner, the configuration information may include: first indication information and resource information of the first sub-application, where the first indication information may be used to indicate whether the first sub-application enables gray-scale release environment; resource information It may include: the grayscale resource address corresponding to the grayscale release environment and the production line resource address corresponding to the production line release environment.

In a possible implementation manner, when the first indication information is the first value, the first indication information indicates that the grayscale publishing environment is enabled; or, when the first indication information is the second value, the first indication information indicates that the Enable grayscale publishing environment.

In a possible implementation manner, the first processing module 602 may also be used to obtain a modification instruction, and the modification instruction is used to switch the first indication information from indicating that the grayscale publishing environment is enabled to indicating that the grayscale publishing environment is not enabled; The apparatus 500 for issuing front-end sub-applications may further include: a modification module, configured to modify the first indication information according to the modification instruction.

In a possible implementation manner, in response to the target publishing environment being a grayscale publishing environment, the sending module 504 may also be configured to: obtain the application corresponding to the grayscale publishing environment by accessing the grayscale resource address corresponding to the grayscale publishing environment resource.

In a possible implementation manner, in response to the fact that the target release environment is the production line release environment, the sending module 504 may also be configured to: obtain the application corresponding to the production line release environment by accessing the production line resource address corresponding to the production line release environment resource.

In a possible implementation manner, the processing module 501 may also be configured to receive a configuration instruction for the first sub-application; the device 500 for releasing the micro-frontier sub-application may further include: a configuration module configured to, according to the configuration instruction, In the source configuration file of the first sub-application, the environment parameters of the gray release environment and/or the environment parameters of the production line release environment are configured; the editing module can be used to edit the configured source configuration file of the first sub-application to obtain The application resources corresponding to the gray release environment and/or the application resources corresponding to the production line release environment.

It should be noted that, the specific implementation process of the processing module 601, the first processing module 602, the second processing module 603, and the sending module 604 can refer to the detailed descriptions of the embodiments in Fig. 1 to Fig. 5 , and for the sake of brevity, details are not repeated here. .

The first processing module 602 and the second processing module 603 mentioned in the embodiment of the present disclosure may be a receiving interface, a receiving circuit, or a receiver, etc.; the sending module 604 may be a sending interface, a sending circuit, or a transmitter, etc.; the processing module 601 may be for one or more processors.

Based on the same inventive concept, an embodiment of the present disclosure provides an electronic device, which may be a release device for micro-front end applications described in one or more embodiments above, or may be a data processing chip. FIG. 7 is a schematic structural diagram of an electronic device in an embodiment of the present disclosure. Referring to FIG. 7 , the electronic device 700 may use general-purpose computer hardware, including a processor 701 and a memory 702 .

In a possible implementation manner, at least one processor 701 may constitute any physical device having a circuit for performing logical operations on one or more inputs. For example, at least one processor may include one or more integrated circuits (ICs), including application specific integrated circuits (ASICs), microchips, microcontrollers, microprocessors, central processing units (central processing units) unit (CPU), all or part of a graphics processing unit (graphics processing unit, GPU), digital signal processor (digital signal process, DSP), field programmable gate array (field programmable gate array, FPGA) or suitable for executing instructions Or other circuits that perform logic operations. The instructions executed by the at least one processor may, for example, be preloaded into a memory integrated with or embedded in the controller, or may be stored in a separate memory. The memory may include random access memory (RAM), read-only memory (ROM), hard disk, optical disk, magnetic media, flash memory, other permanent, fixed, or volatile memory, or capable of storing instructions any other mechanism. In some embodiments, at least one processor may include more than one processor. Each processor may have a similar structure, or the processors may have different configurations that are electrically connected or disconnected from each other. For example, a processor may be a separate circuit or integrated in a single circuit. When more than one processor is used, the processors may be configured to operate independently or cooperatively. Processors may be coupled electrically, magnetically, optically, acoustically, mechanically or by other means allowing their interaction. According to an embodiment of the present disclosure, the present disclosure also provides a computer-readable storage medium, on which computer instructions are stored, and the instructions are executed by a processor to perform the steps of the above-mentioned calibration method. Memory 702 may include computer storage media in the form of volatile and/or non-volatile memory, such as read-only memory and/or random-access memory. Memory 702 may store operating systems, application programs, other program modules, executable code, program data, user data, and the like.

In addition, the memory 702 stores computer-executed instructions for realizing the functions of the processing module 601 , the first processing module 602 , the second processing module 603 and the sending module 604 in FIG. 6 . The functions/implementation processes of the processing module 601, the first processing module 602, the second processing module 603 and the sending module 604 in FIG. 6 can all be implemented by calling the computer execution instructions stored in the memory 702 by the processor 701 in FIG. 7, For the specific implementation process and functions, refer to the related embodiments above.

Based on the same inventive concept, an embodiment of the present disclosure provides an electronic device, including: a memory storing computer-executable instructions; a processor connected to the memory for executing the computer-executable instructions, and capable of implementing the above one or The release method of the micro-frontier sub-application described in multiple embodiments.

Based on the same inventive concept, an embodiment of the present disclosure provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and after the computer-executable instructions are executed by a processor, one or more implementations as described above can be implemented. The release method of the micro front end application described in the example.

Those skilled in the art can understand that the sequence numbers of the steps in the above embodiments do not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, rather than the implementation process of the embodiments of the present disclosure. constitute any limitation.

The above-described embodiments are only used to illustrate the technical solutions of the present disclosure, rather than to limit them; although the present disclosure has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still implement the foregoing embodiments Modifications to the technical solutions described in the examples, or equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present disclosure, and should be included in the within the protection scope of the present disclosure.

Claims (18)

1. A method for issuing micro front end application, which is applied to micro front end main application, the method comprises:

receiving a load instruction for a first sub-application;

acquiring configuration information of the first sub-application according to the loading instruction;

determining a target issuing environment of the first sub-application according to the configuration information;

loading the application resources of the first sub-application for the target publishing environment,

the target issuing environment is a gray level issuing environment or a production line issuing environment.

2. The method of claim 1, wherein determining the target publishing environment of the first sub-application according to the configuration information comprises:

determining whether the first sub-application enables the gray scale publishing environment according to the configuration information;

when the gray scale issuing environment is determined to be started, determining the target issuing environment as the gray scale issuing environment;

and when the gray scale publishing environment is determined not to be started, determining the target publishing environment as the production line publishing environment.

3. The method of claim 1, wherein the configuration information comprises: first indication information and resource information of the first sub-application, wherein,

the first indication information is used for indicating whether the first sub-application enables a gray scale release environment or not;

the resource information includes: and the gray resource address corresponding to the gray release environment and the production line resource address corresponding to the production line release environment.

4. The method according to claim 3, wherein when the first indication information is a first value, the first indication information represents that the grayness issue environment is enabled; or, when the first indication information is a second value, the first indication information represents that the gray scale issuing environment is not enabled.

5. The method of claim 3, further comprising:

acquiring a modification instruction, wherein the modification instruction is used for switching the first indication information from indicating to enable the gray scale issuing environment to indicating not to enable the gray scale issuing environment;

and modifying the first indication information according to the modification instruction.

6. The method of claim 3, wherein in response to the target publication environment being the grayscale publication environment, the loading the application resources of the first sub-application for the target publication environment comprises:

and acquiring the application resource corresponding to the gray scale release environment by accessing the gray scale resource address corresponding to the gray scale release environment.

7. The method of claim 3, wherein, in response to the target publishing environment being the production line publishing environment, the loading the application resources of the first sub-application for the target publishing environment comprises:

and acquiring the application resource corresponding to the production line publishing environment by accessing the production line resource address corresponding to the production line publishing environment.

8. The method of claim 1, wherein prior to said receiving a load instruction for a first sub-application, the method further comprises:

receiving a configuration instruction for the first sub-application;

according to the configuration instruction, configuring the environmental parameters of the gray scale release environment and/or the environmental parameters of the production line release environment in the source configuration file of the first sub-application;

and editing the configured source configuration file of the first sub-application to obtain the application resource corresponding to the gray scale release environment and/or the application resource corresponding to the production line release environment.

9. A device for issuing micro front end applications, the device comprising:

the processing module is used for receiving a loading instruction of the first sub-application;

the first processing module is used for acquiring the configuration information of the first sub-application according to the loading instruction;

the second processing module is used for determining a target issuing environment of the first sub-application according to the configuration information;

a sending module, configured to load application resources of the first sub-application for the target publishing environment,

the target issuing environment is a gray level issuing environment or a production line issuing environment.

10. The apparatus of claim 9, wherein the second processing module is further configured to: determining whether the first sub-application enables the gray scale publishing environment according to the configuration information; when the gray scale issuing environment is determined to be started, determining the target issuing environment as the gray scale issuing environment; and when the gray scale release environment is determined not to be started, determining that the target release environment is the production line release environment.

11. The apparatus of claim 9, wherein the configuration information comprises: first indication information and resource information of the first sub-application, wherein the first indication information is used for indicating whether the first sub-application enables a grey scale release environment or not; the resource information includes: the gray resource address corresponding to the gray release environment and the production line resource address corresponding to the production line release environment.

12. The apparatus of claim 11, wherein when the first indication information is a first value, the first indication information indicates that the grayscale issuing environment is enabled; or, when the first indication information is a second value, the first indication information represents that the gray scale issuing environment is not enabled.

13. The apparatus according to claim 11, wherein the first processing module is further configured to obtain a modification instruction, where the modification instruction is configured to switch the first indication information from indicating that the grayscale issuing environment is enabled to indicating that the grayscale issuing environment is not enabled;

the device further comprises: and the modification module is used for modifying the first indication information according to the modification instruction.

14. The apparatus of claim 11, wherein in response to the target publication environment being the grayscale publication environment, the sending module is further configured to: and acquiring the application resource corresponding to the gray scale release environment by accessing the gray scale resource address corresponding to the gray scale release environment.

15. The apparatus of claim 11, wherein in response to the target publishing environment being the production line publishing environment, the sending module is further configured to: and obtaining the application resource corresponding to the production line release environment by accessing the production line resource address corresponding to the production line release environment.

16. The apparatus of claim 9, wherein the processing module is further configured to receive a configuration instruction for the first sub-application;

the device further comprises: the configuration module is used for configuring the environmental parameters of the gray scale release environment and/or the environmental parameters of the production line release environment in the source configuration file of the first sub-application according to the configuration instruction; and the editing module is used for editing the configured source configuration file of the first sub-application to obtain the application resource corresponding to the gray scale release environment and/or the application resource corresponding to the production line release environment.

17. An electronic device, comprising:

a memory for storing processor-executable instructions;

a processor; wherein the processor is configured to: when being executed, implement the method of any one of claims 1 to 8.

18. A computer-readable storage medium, characterized in that the readable storage medium stores an executable program, wherein the executable program, when executed by a processor, implements the method of any one of claims 1 to 8.

Images