Non-perception upgrading method and system for webpage configuration components and related components

Abstract

The invention discloses a non-perception upgrading method and system for a webpage configuration component, electronic equipment and a computer program product. The method comprises the following steps: collecting a label version of the configuration component in a configuration page; comparing the label version with a latest version in a front-end component library; if the label version is different from the newest version, performing non-perceptual upgrading on the configuration component of the label version based on the configuration component of the corresponding newest version; and carrying out rendering display on the upgraded configuration component. The label versions of the configuration components in the configuration page are collected, and the configuration components of the newest version of the front-end component library are compared and updated according to the label versions, so that non-perceptual upgrading of the configuration components can be realized, the upgrading efficiency of the configuration components is improved, the upgrading complexity of the configuration components is reduced, and the upgrading efficiency of the configuration components is improved. And the purpose of normally rendering the configuration of the page is achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of computer software development, and in particular to a method and system for upgrading web page configuration components without perception, and related components. Background Art

[0002] With the development of visualization technology and the rise of the digital wave, various equipment monitoring systems and visualization management systems have emerged in an endless stream. In some scenarios where low-code configuration development is applied, due to the different user focuses and aesthetic display style requirements, the configuration style and component properties of the configuration components are difficult to fully meet the user's usage requirements. In addition, configuration components may introduce open source third-party public libraries during the development process, and these public library configurations and properties will also be iteratively updated under the author's maintenance. However, there are certain defects in iterative updates. For example, it is not possible to re-edit and configure components in the configuration design editor every time a component is upgraded and updated. Moreover, this method is closely related to the number of configuration pages and the complexity of the layout of each page, and is in a completely uncontrollable manner.

[0003] Therefore, how to seamlessly upgrade the configuration components in the configuration design page and the configuration preview page without affecting user usage and without changing user configuration items and display effects is a problem that technical personnel in this field need to solve. Summary of the invention

[0004] The embodiments of the present invention provide a method, system, electronic device and computer program product for imperceptible upgrade of web page configuration components, aiming to achieve imperceptible upgrade of configuration components, so as to improve the upgrade efficiency of configuration components and reduce the upgrade complexity of configuration components.

[0005] In a first aspect, an embodiment of the present invention provides a method for upgrading a web page configuration component without being perceived, comprising:

[0006] Collect the label version of the configuration components in the configuration page;

[0007] Compare the tag version with the latest version in the front-end component library;

[0008] If the tag version is different from the latest version, the configuration component of the tag version is upgraded imperceptibly based on the configuration component of the corresponding latest version;

[0009] The upgraded configuration components are rendered and displayed.

[0010] In a second aspect, an embodiment of the present invention provides a non-perceptual upgrade system for a web page configuration component, including:

[0011] A collection unit, used for collecting the label versions of the configuration components in the configuration page;

[0012] A comparison unit, used to compare the tag version with the latest version in the front-end component library;

[0013] An upgrading unit, configured to perform a non-perceptual upgrading of the configuration component of the label version based on the corresponding latest version of the configuration component if the label version is different from the latest version;

[0014] The display unit is used to render and display the upgraded configuration components.

[0015] In a third aspect, an embodiment of the present invention provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, a method for imperceptible upgrade of a web page configuration component as in the first aspect is implemented.

[0016] In a fourth aspect, an embodiment of the present invention provides a computer program product. When instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the method for imperceptible upgrade of a web page configuration component as described in the first aspect.

[0017] The embodiment of the present invention provides a method, system, electronic device and computer program product for imperceptible upgrade of web page configuration components, the method comprising: collecting the label version of the configuration component in the configuration page; comparing the label version with the latest version in the front-end component library; if the label version is different from the latest version, imperceptibly upgrading the configuration component of the label version based on the corresponding latest version of the configuration component; rendering and displaying the upgraded configuration component. The present invention collects the label version of the configuration component in the configuration page, and compares and updates the configuration component of the label version according to the latest version of the front-end component library, so as to improve the upgrade efficiency of the configuration component, reduce the upgrade complexity of the configuration component, and achieve the purpose of normal page rendering configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.

[0019] Figure 1 A flowchart of a method for non-perception upgrade of a web page configuration component provided by an embodiment of the present invention;

[0020] Figure 2 A schematic diagram of a first sub-process in a method for non-perception upgrade of a web page configuration component provided by an embodiment of the present invention;

[0021] Figure 3 A schematic diagram of a second sub-process in a method for non-perception upgrade of a web page configuration component provided by an embodiment of the present invention;

[0022] Figure 4 A schematic diagram of a third sub-process in a method for non-perception upgrade of a web page configuration component provided by an embodiment of the present invention;

[0023] Figure 5 A schematic block diagram of a system for seamlessly upgrading a web page configuration component provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0025] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0026] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0027] It should be further understood that the term "and / or" used in the present description and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0028] See below Figure 1 , an embodiment of the present invention provides a method for imperceptible upgrade of a web page configuration component, specifically comprising: steps S101-S104.

[0029] Step S101, collecting the label version of the configuration component in the configuration page;

[0030] Step S102: Compare the tag version with the latest version in the front-end component library;

[0031] After the technician upgrades the configuration component, the upgraded configuration component is stored in the front-end component library, so the version of the configuration component in the front-end component library is the latest version.

[0032] Step S103: If the tag version is different from the latest version, the configuration component of the tag version is upgraded without perception based on the corresponding configuration component of the latest version;

[0033] Step S104: Render and display the upgraded configuration components.

[0034] In this embodiment, the label version of the configuration component in the configuration page is first collected, and then the collected label version is compared with the latest version of the configuration component in the front-end component library, and it is determined whether the label version needs to be upgraded based on the comparison. That is, if the label version is different from the latest version, the label version is upgraded, and if the label version is the same as the latest version, there is no need to upgrade the label version. For the upgraded label version, it is rendered and displayed.

[0035] The present invention collects the label versions of the configuration components in the configuration page, and compares and updates the configuration components of the label versions according to the latest version of the front-end component library, so as to realize the imperceptible upgrade of the configuration components, improve the upgrade efficiency of the configuration components, reduce the upgrade complexity of the configuration components, and achieve the purpose of normal rendering of the configuration of the page.

[0036] In this embodiment, the configuration page is composed of page basic configuration information and N multiple different configuration components. This scheme upgrades the configuration components in the configuration page. Configuration is the process of using tools and methods in application software to complete a specific task in the project. Users can select and configure various tools and components in the software according to their needs to achieve specific functions. The configuration component is a simple encapsulation of data and methods, and the configuration component represents an independent and reusable part on the page. The component can contain its own template, logic, style, attributes and data source, etc., and by combining different components, a complex and feature-rich page can be constructed. The configuration component in this embodiment has no perception upgrade operation, which is to inherit, merge, exclude, and assign default values ​​to the existing style configuration, attribute configuration, and data source configuration of the configuration component. Then the processed configuration attributes are injected into the component, and the upgraded page effect is dynamically rendered by loading the dynamic component to avoid errors and business interruptions caused by manual editing design or program upgrades.

[0037] In actual application scenarios, the label version of the configuration component in the configuration page can be collected through a user interface or other means, and the label version of the configuration component can be quickly obtained when the configuration editing designer or the configuration preview page content data is read.

[0038] In one embodiment, comparing the tag version with the latest version of the configuration component in the front-end component library includes:

[0039] Get the version numbers of the tag version and the latest version;

[0040] Compare the version number of the tagged version with the version number of the latest version;

[0041] If the version number of the tag version is the same as the version number of the latest version, it is determined that the configuration component of the tag version is the same as the configuration component of the latest version;

[0042] If the version number of the tag version is different from the version number of the latest version, it is determined that the configuration component of the tag version is different from the configuration component of the latest version.

[0043] In this embodiment, combined with Figure 2 When the configuration designer and configuration preview page are loaded, all the data of the configuration page is obtained through the interface, and then the component data set is obtained through serialization, and the data is checked to determine whether an upgrade is required. If the data test result is a blank page, there is no need to upgrade, otherwise an upgrade is required. When upgrading, first obtain the component data set and traverse the component data set to extract the component tag labels. Then compare the version number with the latest version of the configuration component in the front-end component library according to the tag label version. The tag version of the configuration component in the configuration page can be obtained through Map<K,V> The storage format is the unique key of the configuration component and the current version number of the component (i.e. the Value in the key-value pair). When comparing versions, the corresponding latest version can be obtained through the unique key of the configuration component and the version number can be compared. If the version numbers are the same, there is no need to upgrade; if the version number of the tag version is smaller than the version number of the latest version, the upgrade process of the configuration component is executed.

[0044] It should be noted that in different configuration target instances, the imperceptible upgrade will not affect the user's existing data source type and configuration. In addition, the configuration component can be imperceptibly upgraded across multiple versions, and the higher version of the configuration component is backward compatible with the lower version. In addition, multiple instances of the same type of component can be imperceptibly upgraded, and the page Dom loading process will not be affected in the component echo of the configuration editing designer and the rendering of the configuration page.

[0045] In one embodiment, comparing the tag version with the latest version of the configuration component in the front-end component library further includes:

[0046] When the version number of the tag version is not obtained, it is directly determined that the configuration component of the tag version is different from the configuration component of the latest version.

[0047] In this embodiment, in a web page configuration data, the same type of configuration component may have multiple versions with different labels or components without version labels in different configuration target instances. Therefore, when the version number of the label version is not obtained, it is determined that the label version of the configuration component of the configuration page is different from the latest version of the configuration component in the front-end component library, that is, the configuration component upgrade process is directly executed.

[0048] Preferably, when the tag version has no version number, in addition to directly executing the configuration component upgrade process, the component version information can be automatically supplemented in the component data set, and the component version number can be set to the version number of the latest version.

[0049] In one embodiment, if the tag version is different from the latest version, the configuration component of the tag version is upgraded imperceptibly based on the corresponding latest version, including:

[0050] Get the key value of the component configuration of the tag version;

[0051] Get the configuration item information of the component configuration of the tag version and the configuration item information of the latest version of the configuration component corresponding to the key value respectively;

[0052] Based on the configuration item information of the component configuration of the tag version and the configuration item information of the latest version of the configuration component corresponding to the key value, extract the difference configuration items between the tag version and the latest version;

[0053] Based on the difference configuration items, the configuration components of the tag version are upgraded without perception.

[0054] In this embodiment, combined with Figure 3 Before performing a non-perceived upgrade, first determine whether an upgrade is required. If the tag version is the latest version, there is no need to upgrade, otherwise an upgrade is required. When performing a non-perceived upgrade, the latest configuration item information of the configuration library component in the current system is obtained according to the component unique key in the component data set, which may specifically include public location information, basic style configuration information, attribute configuration information, and data source configuration information. Subsequently, the difference configuration items between the configuration component configuration item information of the tag version and the latest version are further obtained, and then the tag version is non-perceived upgraded through the difference configuration items. Furthermore, in combination with the following text, it can be seen that after the configuration component of the tag version is non-perceived upgraded through the difference configuration items, Vue component registration, rendering and display (that is, component style and data rendering) and other operations will also be performed, so that the non-perceived upgrade operation is fully realized.

[0055] Among them, Vue is a JavaScript framework for building user interfaces.

[0056] In a specific embodiment, based on the configuration item information of the component configuration of the tag version and the configuration item information of the latest version of the configuration component corresponding to the key value, extracting the difference configuration items between the tag version and the latest version includes:

[0057] Filter the configuration item information of the component configuration of the tag version and the configuration item information of the latest version of the configuration component corresponding to the key value, and their respective public location information and basic style configuration information;

[0058] Remove public location information and basic style configuration information from configuration item information;

[0059] Based on the configuration item information after removing the public location information and basic style configuration information, the difference configuration items between the tag version and the latest version are extracted.

[0060] In this embodiment, when extracting the difference configuration items, first exclude the public location information and basic style configuration information. This type of information belongs to the common attributes of all components and has their own differences, and does not need to be processed in the upgrade process. After excluding the public location information and basic style configuration information, continue to extract the difference configuration items between the label version and the latest version, and perform upgrade processing according to the difference configuration items.

[0061] In another specific embodiment, the configuration item information includes the configuration item and the attribute value of the configuration item, and based on the difference configuration item, the configuration component of the tag version is upgraded without perception, including:

[0062] Exclude the difference configuration items that only exist in the tag version;

[0063] For differential configuration items that exist in both the tagged version and the latest version and whose attribute values ​​are different between the tagged version and the latest version, the configuration item information corresponding to the tagged version is set as the source object, and the configuration item information corresponding to the latest version is set as the target object;

[0064] Assign the source object to the target object so that the attribute value of the target object is overwritten by the attribute value assignment of the source object;

[0065] If there are differential configuration items that only exist in the latest version, the differential configuration items and their attribute values ​​that only exist in the latest version are merged with the differential configuration items after the attribute values ​​are overwritten to generate a configuration component after the tag version is upgraded.

[0066] In this embodiment, in different configuration target instances, when performing an imperceptible upgrade operation, it is first possible to determine in which version the extracted difference configuration items exist. For example, for difference configuration items that only exist in the label version, they can be directly excluded as abandoned attributes. For difference configuration items that only exist in the latest version, they can be directly merged. For difference configuration items that exist in both the label version and the latest version, the attribute values ​​in the label version can be assigned and overwritten with the corresponding attribute values ​​in the latest version by recursive merging of attribute objects. Specifically, the configuration object information after the current component library component is processed is used as the target object, and the component configuration object of the page data is used as the source object. The enumerable attributes of the source object are assigned to the target object, and the value of the object will be directly assigned and overwritten, and the subsequent source object attributes will overwrite the previously assigned attributes. In the recursive merging process here, the attribute value of the target object inherits the attribute value of the source object, and is combined with the operation of merging the difference configuration items that only exist in the latest version to form a new component configuration object, so that the imperceptible automatic upgrade configuration block processing of the component is completed. In actual application scenarios, the above-mentioned single component imperceptible upgrade process can be repeated, and all components that need to be upgraded in the component set can be processed, and the configuration web page data can be re-serialized. Furthermore, after the configuration component completes the imperceptible upgrade, the component configuration data will be updated, serialized and reintegrated into new page data, and the page data is saved based on the front-end IndexedDB browser database and MySQL relational database.

[0067] Among them, IndexedDB is a way to store data on the browser side; MySQL is a relational database management system.

[0068] It should be noted that the difference configuration items of the present embodiment represent configuration items with differences, and the difference lies in the difference of the configuration items, and / or the difference of the attribute values ​​of the configuration items. For the difference configuration items that exist in both the label version and the latest version, the attribute value of the configuration item in the label version is the default value. If the user has changed the attribute value of the configuration item in the label version, there will be a situation where the difference of the difference configuration items lies in the different attribute values. The configuration items in the latest version should inherit the attribute values ​​of the configuration items in the label version to retain the user's personalized settings for the configuration components. Then the difference configuration items and their attribute values ​​that only exist in the latest version are merged with the difference configuration items after overwriting the attribute values, and the above-mentioned excluded public location information and basic style configuration information, as well as the same configuration item information other than the public location information and basic style configuration information of the label version and the latest version, together form the upgraded configuration components. In addition, after completing the imperceptible upgrade operation, the version number of the configuration component in the configuration page is also updated.

[0069] In one embodiment, rendering and displaying the upgraded configuration component includes:

[0070] Serialize page data for configuration components after tag version upgrade;

[0071] The serialized page data is registered with the Vue component and rendered and displayed in the page Dom tree after registration.

[0072] In this embodiment, combined with Figure 4 When performing a non-perceptual upgrade, the configuration page data will be obtained first, and the obtained configuration page data will be processed as component data to achieve a non-perceptual upgrade of the configuration component. After the non-perceptual upgrade of the configuration component is completed, the page data is serialized, and the Vue component is registered, and rendered and displayed in the page document object model (Document Object Model, Dom) tree, such as rendering component styles and data, etc., to achieve a more complete non-perceptual upgrade operation.

[0073] Among them, the DOM tree is a representation method of the Document Object Model, which represents an HTML or XML document as a tree structure. Each node in the DOM tree represents an element in the document, such as an element node, a text node, and an attribute node.

[0074] In actual applications, when performing a non-perceptual upgrade of web page configuration components, the browser can directly access the corresponding page resource address, and obtain the web page text data through the Axios interface to execute the non-perceptual upgrade process. This ensures that after the upgrade is completed, any client browser can parse and reverse render to display the corresponding web page and data, thereby achieving the purpose of non-perceptual upgrade of components without re-arrangement and business interruption.

[0075] Among them, Axios is a Promise-based HTTP client for browsers and Node.js environments.

[0076] Figure 5 A schematic block diagram of a non-perceptual upgrade system 500 for a web page configuration component provided by an embodiment of the present invention, the system 500 includes:

[0077] The collecting unit 501 is used to collect the tag version of the configuration component in the configuration page;

[0078] A comparison unit 502, used to compare the tag version with the latest version in the front-end component library;

[0079] An upgrading unit 503 is configured to perform a non-perceptual upgrading of the configuration component of the label version based on the configuration component of the corresponding latest version if the label version is different from the latest version;

[0080] The display unit 504 is used to render and display the upgraded configuration components.

[0081] In one embodiment, the comparison unit 502 includes:

[0082] A version number obtaining unit, used to obtain the version numbers of the tag version and the latest version;

[0083] A version number comparison unit, used to compare the version number of the tag version with the version number of the latest version;

[0084] A first determination unit, configured to determine that the configuration component of the tag version is the same as the configuration component of the latest version if the version number of the tag version is the same as the version number of the latest version;

[0085] The second determination unit is configured to determine that the configuration component of the label version is different from the configuration component of the latest version if the version number of the label version is different from the version number of the latest version.

[0086] In one embodiment, the comparison unit 502 further includes:

[0087] The third determination unit is configured to directly determine whether the configuration component of the tag version is different from the configuration component of the latest version when the version number of the tag version is not obtained.

[0088] In one embodiment, the upgrading unit 503 includes:

[0089] The key value acquisition unit is used to obtain the key value of the tag version;

[0090] A configuration acquisition unit, used to respectively acquire configuration item information of the component configuration of the tag version and configuration item information of the latest version of the configuration component corresponding to the key value;

[0091] A first extraction unit is used to extract the difference configuration items between the label version and the latest version based on the configuration item information of the component configuration of the label version and the configuration item information of the latest version of the configuration component corresponding to the key value;

[0092] The difference upgrade unit is used to perform a non-perceptual upgrade of the configuration components of the tag version based on the difference configuration items.

[0093] In one embodiment, the first extraction unit includes:

[0094] A configuration screening unit, used to screen the configuration item information of the component configuration of the tag version and the configuration item information of the latest version of the configuration component corresponding to the key value, the respective configuration component public position information and basic style configuration information;

[0095] A configuration elimination unit, used to eliminate the public location information and basic style configuration information from the configuration item information;

[0096] The second extraction unit is used to extract the difference configuration items between the tag version and the latest version based on the configuration item information after removing the public location information and the basic style configuration information.

[0097] In one embodiment, the configuration item information includes the configuration item and the attribute value of the configuration item, and the difference upgrade unit includes:

[0098] Exclusion unit, used to exclude differential configuration items that only exist in the tag version;

[0099] The object setting unit is used to set the configuration item information corresponding to the label version as the source object and the configuration item information corresponding to the latest version as the target object for the difference configuration items that exist in both the label version and the latest version and whose attribute values ​​are different between the label version and the latest version;

[0100] An overwriting unit, used for allocating the source object to the target object so that the attribute value of the target object is overwritten by the attribute value allocation of the source object;

[0101] The merging unit is used to merge the difference configuration items and their attribute values ​​that only exist in the latest version with the difference configuration items after overwriting the attribute values, if there are difference configuration items that only exist in the latest version, so as to generate a configuration component after the tag version is upgraded.

[0102] In one embodiment, the display unit 504 includes:

[0103] A serialization processing unit is used to perform page data serialization processing on the configuration component after the latest version upgrade;

[0104] The registration rendering unit is used to register the serialized page data with the Vue component, and render and display it in the page Dom tree after registration.

[0105] Since the embodiments of the system part correspond to the embodiments of the method part, please refer to the description of the embodiments of the method part for the embodiments of the system part, which will not be repeated here.

[0106] The embodiment of the present invention also provides an electronic device, which may include a memory and a processor, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, the steps provided in the above embodiment may be implemented. Of course, the electronic device may also include various network interfaces, power supplies and other components.

[0107] The embodiment of the present invention also provides a computer program product, on which a computer program is stored, and when the computer program is executed, the steps provided in the above embodiment can be implemented. The computer program product may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0108] The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the various embodiments can be referred to each other. For the system disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of this application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of this application.

[0109] It should also be noted that, in this specification, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

Claims

1. A method for upgrading a web page configuration component without any perception, characterized in that: include: Collect the label version of the configuration components in the configuration page; Compare the tag version with the latest version in the front-end component library; If the tag version is different from the latest version, the configuration component of the tag version is upgraded imperceptibly based on the configuration component of the corresponding latest version; The upgraded configuration components are rendered and displayed.

2. The method for upgrading a web page configuration component without perception according to claim 1, characterized in that: The comparing the tag version with the latest version in the front-end component library includes: Get the version numbers of the tag version and the latest version respectively; Compare the version number of the tag version with the version number of the latest version; If the version number of the label version is the same as the version number of the latest version, then it is determined that the configuration component of the label version is the same as the configuration component of the latest version; If the version number of the label version is different from the version number of the latest version, it is determined that the configuration component of the label version is different from the configuration component of the latest version.

3. The method for upgrading the webpage configuration component without perception according to claim 2, characterized in that: The comparing the tag version with the latest version in the front-end component library also includes: When the version number of the label version is not obtained, it is directly determined that the configuration component of the label version is different from the configuration component of the latest version.

4. The method for upgrading a web page configuration component without perception according to claim 1, characterized in that: If the tag version is different from the latest version, the configuration component of the tag version is upgraded imperceptibly based on the configuration component of the corresponding latest version, including: Get the key value of the component configuration of the tag version; Respectively obtain the configuration item information of the component configuration of the tag version and the configuration item information of the latest version of the configuration component corresponding to the key value; Based on the configuration item information of the component configuration of the label version and the configuration item information of the latest version of the configuration component corresponding to the key value, extract the difference configuration items between the label version and the latest version; Based on the difference configuration items, the configuration components of the tag version are upgraded imperceptibly.

5. The method for upgrading a web page configuration component without perception according to claim 4, characterized in that: The configuration item information of the component configuration based on the label version and the configuration item information of the latest version of the configuration component corresponding to the key value, extracting the difference configuration items between the label version and the latest version, includes: Filter the configuration item information of the component configuration of the tag version and the configuration item information of the latest version of the configuration component corresponding to the key value, and their respective public location information and basic style configuration information; Remove the public location information and basic style configuration information from the configuration item information; Based on the configuration item information after removing the public location information and the basic style configuration information, the difference configuration items between the label version and the latest version are extracted.

6. The method for upgrading a web page configuration component without perception according to claim 4, characterized in that: The configuration item information includes configuration items and attribute values ​​of configuration items, and the step of performing a non-perceptual upgrade on the configuration component of the tag version based on the difference configuration items includes: Exclude the difference configuration items that only exist in the tag version; For differential configuration items that exist in both the tagged version and the latest version and whose attribute values ​​are different between the tagged version and the latest version, the configuration item information corresponding to the tagged version is set as the source object, and the configuration item information corresponding to the latest version is set as the target object; Allocating the source object to the target object so that the attribute value of the target object is overwritten by the attribute value of the source object; If there are differential configuration items that only exist in the latest version, the differential configuration items and their attribute values ​​that only exist in the latest version are merged with the differential configuration items after the attribute values ​​are overwritten to generate a configuration component after the tag version is upgraded.

7. The method for upgrading a web page configuration component without perception according to claim 1, characterized in that: The rendering and displaying of the upgraded configuration components includes: Serialize page data for upgraded configuration components; The serialized page data is registered with the Vue component and rendered and displayed in the page Dom tree after registration.

8. A non-perception upgrade system for web page configuration components, characterized in that: include: A collection unit, used for collecting the label versions of the configuration components in the configuration page; A comparison unit, used to compare the tag version with the latest version in the front-end component library; An upgrading unit, configured to perform a non-perceptual upgrading of the configuration component of the label version based on the corresponding latest version of the configuration component if the label version is different from the latest version; The display unit is used to render and display the upgraded configuration components.

9. An electronic device, characterized in that: It comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method for imperceptible upgrade of a web page configuration component as described in any one of claims 1 to 7 is implemented.

10. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the imperceptible upgrade method of the web page configuration component as described in any one of claims 1-7.

Images