An assembly updating method, processing method, device and electronic equipment

Abstract

The present disclosure provides a component updating method, a processing method, a device and an electronic device, relates to the technical field of computers, and in particular to the technical field of data processing. A component of one embodiment comprises a specification component, and the component updating method comprises: receiving a style editing operation on the specification component; updating an original style of the specification component according to the style editing operation to obtain a target style of the specification component; obtaining a specification instance referencing the specification component; and updating the specification instance according to the target style of the specification component, which can optimize the updating range of the component and improve the component publishing efficiency.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, specifically to the field of data processing technology, and in particular to a component updating method, processing method, apparatus, electronic device, computer-readable storage medium, and computer program product. Background Technology

[0002] In recent years, front-end componentization has become the mainstream development model for front-end projects, and building component libraries has become an essential path for every front-end technology team to grow. Traditional front-end public component libraries are designed as a "one-stop shop," meaning that when any component has a defect or needs to be updated, the entire library will be released and upgraded. Summary of the Invention

[0003] This disclosure provides a component update method, processing method, apparatus, electronic device, computer-readable storage medium, and computer program product that can optimize the scope of component updates and improve component release efficiency.

[0004] According to one aspect of this disclosure, a component update method is provided, wherein the component includes a specification component, the update method comprising:

[0005] Receive style editing operations on a specification component; update the original style of the specification component according to the style editing operations to obtain the target style of the specification component; obtain a specification instance that references the specification component; update the specification instance according to the target style of the specification component.

[0006] According to another aspect of this disclosure, a component processing method is provided, the processing method comprising:

[0007] Create a document instance and determine the style data of the document instance; publish the document instance to obtain the specification component corresponding to the style data and the specification instance referencing the specification component; determine the target source component referenced by the specification component based on the style data.

[0008] According to another aspect of this disclosure, a component updating apparatus is provided, wherein the component includes a specification component, and the updating apparatus includes:

[0009] A receiving module is configured to receive style editing operations on a specification component; a first updating module is configured to update the original style of the specification component according to the style editing operation to obtain the target style of the specification component; an obtaining module is configured to obtain a specification instance that references the specification component; and a second updating module is configured to update the specification instance according to the target style of the specification component.

[0010] According to another aspect of this disclosure, a component processing apparatus is provided, the processing apparatus comprising:

[0011] A creation module is configured to create a document instance and determine the style data of the document instance; a publishing module is configured to publish the document instance to obtain the specification component corresponding to the style data and the specification instance referencing the specification component; a determination module is configured to determine the target source component referenced by the specification component based on the style data.

[0012] According to another aspect of this disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the aforementioned component update method or component processing method.

[0013] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause the computer to perform the aforementioned component update method or component processing method.

[0014] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the aforementioned component update method or component processing method.

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

[0016] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0017] Figure 1 This is an exemplary system architecture diagram in which one embodiment of this application can be applied;

[0018] Figure 2 This is a flowchart of one embodiment of the component update method according to this application;

[0019] Figure 3 This is a schematic diagram of a specification library according to an embodiment of this application;

[0020] Figure 4 This is a schematic diagram illustrating the range of component updates according to an embodiment of this application;

[0021] Figure 5This is a flowchart of yet another embodiment of the component update method according to this application;

[0022] Figure 6 A schematic diagram of the document library according to an embodiment of this application;

[0023] Figure 7 Another schematic diagram of the document library according to an embodiment of this application;

[0024] Figure 8 This is a flowchart of one embodiment of the component processing method according to this application;

[0025] Figure 9 This is a schematic diagram illustrating a scenario of a published document instance or document component according to embodiments of this application;

[0026] Figure 10 This is another scenario illustration of a published document instance or document component according to the embodiments of this application;

[0027] Figure 11 This is a flowchart of yet another embodiment of the component processing method according to this application;

[0028] Figure 12 This is yet another schematic diagram of a specification library according to an embodiment of this application;

[0029] Figure 13 This is a schematic diagram illustrating a scenario of a combined release example according to an embodiment of this application;

[0030] Figure 14 This is a schematic diagram illustrating the selection of the update range of the combined source components according to an embodiment of this application;

[0031] Figure 15 This is a schematic diagram of a component update apparatus according to an embodiment of the present application;

[0032] Figure 16 This is a schematic diagram of the structure of one embodiment of the component processing apparatus according to this application;

[0033] Figure 17 This is a block diagram of an electronic device used to implement the component update method or component processing method of the embodiments of this disclosure. Detailed Implementation

[0034] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0035] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0036] Figure 1 An exemplary system architecture is shown, in which embodiments of the component update method and component processing method of this application can be applied.

[0037] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing communication links between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0038] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Terminal devices 101, 102, and 103 can have applications for component development installed, such as front-end design applications or real-time design applications.

[0039] Terminal devices 101, 102, and 103 can be either hardware or software. When terminal devices 101, 102, and 103 are hardware, they can be various electronic devices, including but not limited to smartphones, tablets, e-book readers, laptops, and desktop computers. When terminal devices 101, 102, and 103 are software, they can be installed in the aforementioned electronic devices. They can be implemented as multiple software programs or software modules (e.g., to provide distributed services) or as a single software program or software module. No specific limitations are imposed here.

[0040] Server 105 can be a server that provides various services, such as a backend server that updates or processes components generated by users through terminal devices 101, 102, and 103. The backend server can publish and update the obtained components and feed back the processing results (such as the component update results) to terminal devices 101, 102, and 103.

[0041] It should be noted that server 105 can be either hardware or software. When server 105 is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When server 105 is software, it can be implemented as multiple software programs or software modules (e.g., used to provide distributed services), or as a single software program or software module. No specific limitations are made here.

[0042] It should be understood that Figure 1The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0043] It should be noted that the component update method and component processing method provided in this application embodiment are generally executed by server 105. Accordingly, the component update device and component processing device are generally disposed in server 105.

[0044] Figure 2 A schematic flowchart of a component update method according to an embodiment of this application is shown. The specific steps of the method are as follows:

[0045] Step 20: Receive style editing operations for the standard components.

[0046] This step aims to update the execution body of the method by the component (e.g., Figure 1 The server 105 shown receives style editing operations on the specification components. For example, Figure 3 As shown, the specification components are stored in the specification library. The style editing operation includes updating operations such as modifying or editing the style of the specification components. It should be understood that the specification components may include styles such as color, font or layout, and this application does not limit them.

[0047] Step 21: Update the original style of the standardized component according to the style editing operation to obtain the target style of the standardized component.

[0048] After receiving a style edit operation on a specification component, this step is intended for the execution body of the component update method (e.g., Figure 1 The server 105 shown updates the original style of the specification component based on the style editing operation to obtain the target style of the specification component. For example, the style editing operation can be analyzed to determine what kind of editing modification was performed on the original style of the specification component. For example, if the original style of the specification component is red, regular script, and centered, and the style editing operation modifies the original style of the specification component to black, Song script, and left alignment, then it can be determined that the target style of the updated specification component is black, Song script, and left alignment.

[0049] Step 22: Obtain the specification instance of the reference specification component.

[0050] This step aims to update the execution body of the method by the component (e.g., Figure 1The server 105 shown obtains specification instances that reference specification components. These specification instances are stored in a document library. The executing entity can filter specification instances that reference specification components from the document library. It should be understood that when a specification instance and a specification component have a reference relationship, the style data of the specification instance is the same as the style data of the specification component. Therefore, the executing entity can also obtain specification instances that reference specification components by filtering specification instances with the same style data as the specification component from the document library.

[0051] In some alternative embodiments of this example, the executing entity may also obtain a first list of referenced components of the specification and determine the specification instance based on the first list of referenced components.

[0052] like Figure 3 As shown, the specification library stores Document 1 - Specification Component C1, Document 2 - Specification Component C2, and Document 3 - Specification Component D1. The library also stores the reference relationships between specification instances and specification components, aggregating these relationships into a first referenced list, which is displayed within the specification components. Taking Document 1 - Specification Component C1 as an example, the first referenced list for Document 1 - Specification Component C1 consists of instances C1.1, C1.2, and C1.3. Business personnel then... Figure 3 The document 1 - specification component C1 shown can know the specification instances that have a reference relationship with specification component C1, and according to the first referenced list, it filters the specification instances that exist on the first referenced list in the document library, that is, it filters the document library for instances C1.1, instances C1.2 and instances C1.3, and determines instances C1.1, instances C1.2 and instances C1.3 as specification instances, thereby improving the accuracy of determining specification instances.

[0053] Furthermore, it should be noted that those skilled in the art can store the various specification components in corresponding folders according to actual storage needs, for example, such as Figure 3 As shown, Document 1 - Specification Component C1 and Document 2 - Specification Component C2 are stored in folder 1; Document 3 - Specification Component D1 is stored in subfolder C2 under folder 1. This establishes a clear hierarchical storage method, allowing for easy access to updated specification components later. Figure 4 By selecting different folders in the source component node shown, the update scope of the component can be determined, thereby optimizing the update of the component.

[0054] Furthermore, it should be noted that specification components with the same style but different source documents can be created repeatedly. For example, specification components C1 and C2 both contain style data 'c'. Since specification component C1 originates from document 1 and specification component C2 originates from document 2, specification components C1 and C2 can be created simultaneously in the specification library. The specification components can be named according to their source documents, such as Document 1 - Specification Component C1 and Document 2 - Specification Component C2, to distinguish specification components with the same style. Additionally, when updating specification components subsequently, this can be achieved through... Figure 4 By selecting different documents in the source component node shown, the scope of component updates can be determined, thereby optimizing and updating the component.

[0055] Step 23: Update the specification instance according to the target style of the specification component.

[0056] After step 22 identifies the specification instance that has a reference relationship with the specification component, this step aims to have the execution body of the method updated by the component (e.g., Figure 1 The server 105 shown updates the specification instance according to the target style of the specification component.

[0057] In this embodiment, step 21 determines the target style of the specification component. Since the style data of the specification instance needs to be synchronized with the style data of the specification component, after updating the specification component, the specification instance also needs to be updated to update the original style data of the specification instance to the target style. The previous example will be used for illustration, where, for example... Figure 3 As shown, the original style of the specification component C1 in document 1 is red, KaiTi font, and centered. The target style of the specification component is black, SongTi font, and left-aligned. Therefore, the specification instances that reference the specification component (such as instances C1.1, C1.2, and C1.3) need to be updated from the original style of red, KaiTi font, and centered to the target style of black, SongTi font, and left-aligned to update the specification instances. It should be understood that the style data of the updated specification instances is black, SongTi font, and left-aligned.

[0058] In this embodiment, the original style of the standard component is updated according to the style editing operation to obtain the target style of the standard component. Based on the target style of the standard component, the update operation of the standard instance that references the standard component is implemented, which can optimize the update method of the component and realize the synchronization of style updates between the component and the instance.

[0059] See Figure 5 This application illustrates a schematic flowchart of another embodiment of the component update method, the specific steps of which are as follows:

[0060] Step 30: Receive style editing operations for the source component.

[0061] This step aims to update the execution body of the method by the component (e.g., Figure 1 The server 105 shown receives style editing operations on the source component. In practical applications, such as... Figure 3 As shown, the components stored in the specification library also include source components. The style editing operation also includes update operations such as modifying or editing the style of the source component. It should be understood that the source component may include styles such as color, font or layout, which is not limited in this application.

[0062] It's important to note that the source component is referenced by the canonical component; that is, there is a reference relationship between the source component and the canonical component, and the style data of the source component is the same as the style data of the canonical component. More specifically, for example... Figure 3 As shown, the specification library includes a specification link resource layer and a document specification layer. Source components are stored in the specification link resource layer, and specification components are stored in the document specification layer.

[0063] Step 31: Update the original style of the source component according to the style editing operation to obtain the target style of the source component.

[0064] After receiving a style edit operation on the source component, this step is intended for the execution body of the component update method (e.g., Figure 1 The server 105 shown updates the original style of the source component based on the style editing operation to obtain the target style of the source component. For example, the style editing operation can be analyzed to determine how the style editing operation modified the original style of the source component. For example, if the original style of the source component is red, regular script, and centered, and the style editing operation modifies the original style of the source component to black, Song script, and left-aligned, then it can be determined that the updated target style of the source component is black, Song script, and left-aligned.

[0065] Step 32: Obtain the canonical component that references the source component.

[0066] This step aims to update the execution body of the method by the component (e.g., Figure 1 The server 105 shown obtains the specification components that reference the source component. As mentioned above, the specification components are stored in the document specification layer of the specification library. The executing entity can obtain the specification components that reference the source component by filtering the specification components that have a reference relationship with the source component from the document specification layer, and also by filtering the specification components that have the same style data as the source component from the document specification layer.

[0067] In some alternative embodiments of this example, the executing entity may also obtain a second list of referenced source components; and determine the specification components based on the second list of referenced components.

[0068] like Figure 3As shown, the specification library stores source component C* and source component D*. Furthermore, the specification library also stores the reference relationships between source components and specification components, aggregating these reference relationships into a second referenced list, which is displayed in the source components. For example, the style data of source component C* is c, and its referenced list includes document 1 - specification component C1 and document 2 - specification component C2; the style data of source component D* is d, and its referenced list includes document 3 - specification component D3. Business personnel based on... Figure 3 The source component shown can identify the specification components that have a reference relationship with the source component, and based on the second referenced list, filter the specification components that exist on the second referenced list in the document specification layer of the specification library, thereby improving the accuracy of identifying specification components.

[0069] Step 33: In response to the canonical component being set to receive style updates, receive the target style of the source component through the canonical component.

[0070] Generally, the style data of a specification component needs to be synchronized with the style data of the source component. However, in this embodiment, after updating the original style of the source component to the target style, the specification component can choose whether to accept the target style and whether to update the original data of the specification component to the target style according to the actual situation. Compared with the prior art, when any component has a defect or needs to be updated, the update scheme of this application is more intelligent, improves the stability of the components, and can effectively avoid the impact of updating or iterative upgrading of one component on the functional stability of other components.

[0071] Therefore, this step aims to update the execution body of the method by the component (e.g., Figure 1 The server 105 shown receives the target style of the source component in response to the canonical component being set to receive style updates. That is, after the original style of the source component is updated, the canonical component only needs to be updated when it is set to receive style updates, thereby updating the original style of the canonical component to the target style.

[0072] Step 34: Update the original style of the specification component according to the target style of the source component to obtain the target style of the specification component.

[0073] This step aims to update the execution body of the method by the component (e.g., Figure 1 The server 105 shown updates the original style of the canonical component according to the target style of the source component, thus obtaining the target style of the canonical component. The previous example will be used for illustration. Figure 3As shown, the original style of the source component C* is red, KaiTi font, and centered, while the target style of the source component C* is black, SongTi font, and left-aligned. Therefore, the specification components (Document 1 - Specification Component C1 and Document 2 - Specification Component C2) that reference the source component need to be updated from their original style of red, KaiTi font, and centered to their target style of black, SongTi font, and left-aligned to update the specification components. It should be understood that the updated style data of the specification components (Document 1 - Specification Component C1 and Document 2 - Specification Component C2) will be black, SongTi font, and left-aligned.

[0074] Step 35: Obtain the specification instance of the reference specification component.

[0075] In this embodiment, the description of step 35 is the same as that of step 22, and will not be repeated here.

[0076] Step 36: Update the specification instance according to the target style of the specification component.

[0077] In this embodiment, the description of step 36 is the same as that of step 23, and will not be repeated here.

[0078] Furthermore, it should be noted that in this embodiment, when the style data in the source component is updated, it can be done by... Figure 4 By selecting different documents or folders in the source component node shown, the scope of component updates can be determined, effectively avoiding the impact of one component update or iteration upgrade on the functional stability of other components, thereby achieving optimized component updates.

[0079] Step 37: In response to the specification component being set to refuse updates, delete the specification component and replace the specification instance that references the specification component with a document instance, where the document instance references the document component.

[0080] In this embodiment, when the specification component is set to refuse to update, that is, the specification component does not accept the target style of the source component, it is determined that the target style of the source component and the style data of the specification component will no longer be synchronized. Therefore, it is necessary to delete the specification component that references the source component, delete the reference relationship between the specification component that refuses to update and the source component in the second reference list, and replace the specification instance that references the specification component with the document instance.

[0081] The document instance references the document component; both the document instance and the document component are stored in the document library. More specifically, such as... Figure 6 As shown, the document library includes a document link resource layer and a document canvas layer. Document instances are stored in the document canvas layer, and document components are stored in the document link resource layer. When the style data of a document instance and a document component are the same, a reference relationship is established between them. In other words, when there is a reference relationship between a document instance and a document component, their style data are the same.

[0082] like Figure 3 As shown, when Document 1-Specification Component C1 is set to refuse updates, Document 1-Specification Component C1 needs to be deleted. Simultaneously, Document 1-Specification Component C1 should be removed from the referenced list of source component C*, and, as follows... Figure 6 As shown, the specification instance that references the specification component is replaced with a document instance. For example, the reference relationship between specification instance C1.2 and document 1 - specification component C1 is replaced with the reference to document component C1, and the document instance C1.2 is obtained accordingly.

[0083] In addition, it should be noted that multiple documents can be created in the document library, each including examples of different style data, such as... Figure 6 As shown, document 1 includes instances C1.1, C1.2, and C1.3 with style data 'c', and instance D1.4 with style data 'd', and document 1 is stored in folder 1; as Figure 7 As shown, document 3 includes instances E3.1 and E3.2 with style data 'e', ​​and instance F3.3 with style data 'f'. Document 3 is stored in subfolder 2 of folder 1, thus establishing a clear hierarchical storage method. This allows for efficient updates to the document components later. Figure 4 In the source component node shown, different folders and documents can be selected to determine the scope of component updates, thereby optimizing and updating the component.

[0084] Step 38: In response to the canonical component being set to ignore updates, maintain the reference relationship between the canonical component and the source component.

[0085] In this embodiment, when the specification component is set to ignore updates, that is, the specification component temporarily chooses not to accept the target style of the source component, the execution entity maintains the reference relationship between the specification component and the source component, such as... Figure 3 As shown, when Document 1-Specification Component C1 is set to ignore updates, the reference list of source component C* remains unchanged, and the reference relationship between source component C* and Document 1-Specification Component C1 is still maintained. At the same time, source component C* can push updates to Document 1-Specification Component C1 again.

[0086] In this embodiment, by setting the specification component to freely choose whether to receive updates, and by updating the style data of the source component, the update of the relevant specification components and specification instances is effectively optimized, thus improving the component update method.

[0087] See Figure 8 This application illustrates a schematic flowchart of an embodiment of a component processing method, the specific steps of which are as follows:

[0088] Step 40: Create a document instance and determine the style data for the document instance.

[0089] This step is intended for the execution body of the component processing method (e.g., Figure 1 The server 105 shown creates a document instance and determines the style data of the document instance, for example, such as Figure 7 As shown, business personnel create a document instance C1.1 in document 1 of folder 1 in the document canvas layer of the document library according to actual needs. For example, document instance C1.1 can be a design document for a front-end page, which is not limited in this application. After creating document instance C1.1, the style data of document instance C1.1 is further determined, such as determining that the color of the document instance is red, the font is KaiTi, and the layout is centered, and the style is named style data c.

[0090] Step 41: Publish the document instance to obtain the specification components corresponding to the style data and the specification instances that reference the specification components.

[0091] This step is intended for the execution body of the component processing method (e.g., Figure 1 The server 105 shown publishes the document instance, obtaining the specification component corresponding to the style data and the specification instance referencing the specification component. Taking the aforementioned style data example, the style data of the created document instance is determined to be red, in regular script, and centered. After the document instance is published, the style data, also red, in regular script, and centered, can be obtained in the document specification layer of the specification library. At the same time, the document instance becomes a specification instance, the style data of the specification instance is red, in regular script, and centered, and a reference relationship is established between the specification instance and the specification component.

[0092] For example, after creating document instance C1.1, you can directly publish document instance C1.1 to the specification library, thereby enabling it to function as follows: Figure 3 The document specification layer shown obtains the document 1-specification component C1 corresponding to style data c, and at the same time, as Figure 6 As shown, after publication, document instance C1.1 becomes a specification instance that references document 1 - specification component C1.

[0093] Step 42: Based on the style data, determine the target source component referenced by the specification component.

[0094] This step is intended for the execution body of the component processing method (e.g., Figure 1 The server 105 shown determines the target source component referenced by the specification component based on the style data. The target source component is stored in the link resource layer of the specification library. The style data of the specification component is the same as the style data of the target source component. The executing entity can filter source components with the same style data as the specification component in the specification link resource layer as target source components and establish a reference relationship between the specification component and the target source component.

[0095] In some optional embodiments of this example, the target source component may also be determined through the following steps:

[0096] In response to obtaining a candidate source component that matches the style data from the specification library, the candidate source component is used as the target document component, and the association with the specification component is added to the reference list of the candidate source component.

[0097] For example, such as Figure 3 As shown, in the canonical link resource layer, there is a source component C* with style data c. Since the style data of document 1-canonical component C1 is c, a candidate source component matching the style of the canonical component can be found in the canonical link resource layer. At this time, document 1-canonical component C1 needs to be added to the reference list of source component C*, that is, the reference relationship between source component C* and document 1-canonical component C1 is established.

[0098] In response to the failure to obtain a candidate source component that matches the style data from the specification library, a target source component corresponding to the style data is created, and the association with the specification component is added to the reference list of the target source component.

[0099] For example, such as Figure 3 As shown, in the specification link resource layer, there is a source component C* with style data c, and the style data of document 3-specification component D1 is d. That is, the executing entity cannot find a candidate source component that matches the style of the specification component in the specification link resource layer. At this time, it is necessary to create a target source component corresponding to style data d in the specification link resource layer, such as source component D*. At the same time, add document 3-specification component D1 to the reference list of source component D*, that is, establish a reference relationship between source component C* and document 3-specification component D1.

[0100] In the specification library of this embodiment, a set of bidirectional links is established between specification components and source components. The specification component references the specification source component, and the specification component automatically appears in the reference list of the source component. A set of bidirectional links is established between the specification components in the specification library and the specification instances in the document library. The specification instance references the specification component, and the specification instance automatically appears in the reference list of the specification component.

[0101] See Figure 9 The diagram illustrates two scenarios for publishing document instances. Instance C1.3 can be directly published to the specification library to obtain document 1 - specification component C1. Alternatively, document component C1, including instances C1.1, C1.2, and C1.3, can be published to the specification library to obtain document 1 - specification component C1. Furthermore, when the style data of document component C1 changes, it can be synchronously pushed to all instances to update their style data.

[0102] See Figure 10 This diagram illustrates a scenario where a source component is created based on a specification component. For example, when the style data of document 1 - specification component C1 is the same as that of specification source component C*, they can be automatically referenced, establishing a reference relationship between document 1 - specification component C1 and specification source component C*. Simultaneously, when a document instance is published, such as instance C2.3, it is determined that it has already been published as document 2 - specification component C2. In this case, there is no need to republish instance C2.3; simply re-associate instance C2.3 with document 2 - specification component C2. Furthermore, when creating document instance C2.2, if its style data is the same as that of a document component, it can be automatically referenced, establishing a bidirectional link relationship between the document instance and the document component.

[0103] In this embodiment, by publishing a document instance, the specification component corresponding to the style data and the specification instance referencing the specification component are obtained, and the target source component referenced by the specification component is determined. This enables the establishment of a bidirectional link relationship between the target source component and the specification component. Thus, when the style data of the source component is subsequently updated, the specification component that needs to be updated can be accurately determined based on this bidirectional link relationship, thereby improving update efficiency and component stability.

[0104] In this embodiment, the platform's team specification library is a publicly accessible linked resource. Multiple source documents can be created within this resource, and components with identical styles can be repeatedly published within these source documents. All design documents within the team can reference linked components from the specification library, generating linked component instances within the documents for creation. When a linked component in a source document is modified, all documents containing that component will receive an update notification. Subsequently, in the relevant documents, users can choose to preview and accept the update.

[0105] See Figure 11 This application illustrates a schematic flowchart of another embodiment of the component processing method, the specific steps of which are as follows:

[0106] Step 50: Create a document instance and determine the style data for the document instance.

[0107] In this embodiment, the description of step 50 is the same as that of step 40, and will not be repeated here.

[0108] Step 51: Based on the style data, determine the target document component referenced by the document instance.

[0109] This step is intended for the execution body of the component processing method (e.g., Figure 1The server 105 shown determines the target document component referenced by the document instance based on the style data. The target document component is stored in the document link resource layer of the document library. The style data of the document instance is the same as the style data of the target document component. The executing entity can filter document components with the same style data as the document instance in the document link resource layer as the target document component and establish a reference relationship between the document instance and the target document component.

[0110] In some optional embodiments of this example, the target document component referenced by the document instance can also be determined based on the style data through the following steps:

[0111] In response to retrieving a candidate document component that matches the style data from the document library, the candidate document component is used as the target document component, and the association with the document instance is added to the reference list of the candidate document component.

[0112] like Figure 6 The document link resource layer of the document library includes a document component C1 with style data c, and a document instance C1.2 with style data c. This means that a candidate document component matching the style data can be obtained from the document library. The candidate document component is then used as the target document component, i.e., document component C1 is used as the target document component. Document instance C1.2 is added to the reference list of document component C1, establishing a reference relationship between document instance C1.2 and document component C1.

[0113] In response to the failure to find a candidate document component that matches the style data from the document library, a target document component corresponding to the style data is created, and the association with the document instance is added to the reference list of the target document component.

[0114] like Figure 6 The candidate document components in the document link resource layer of the document library include document component C1, whose style data is c, and the style data of the created document instance D1.4 is d. That is, no candidate document component matching the style data can be obtained from the document library. At this time, it is necessary to create a target document component corresponding to the style data d, namely document component D1, and at the same time add document instance D1.4 to the reference list of document component D1 to establish a reference relationship between document instance D1.4 and document component D1.

[0115] Step 52: Publish the document instance by publishing the target document component.

[0116] This step is intended for the execution body of the component processing method (e.g., Figure 1The server 105 shown publishes document instances by publishing the target document component. In other words, compared to the method of directly publishing document instances after creating them in the previous embodiment, this application can first associate document instances with the same style data with the target document component, and then publish the target document component to achieve simultaneous publication of multiple document instances, effectively improving the publication efficiency of document instances.

[0117] For example, such as Figure 6 As shown, document component C1 includes document instances C1.1, C1.2, and C1.3 with the same style. By publishing document component C1, document instances C1.1, C1.2, and C1.3 can be published.

[0118] Step 53: Publish the document instance to the specification library to obtain the specification component corresponding to the style data.

[0119] This step is intended for the execution body of the component processing method (e.g., Figure 1 The server 105 shown publishes the document instance to the specification library, obtaining the specification component corresponding to the style data. For example, after publishing the target document component C1, the document 1-specification component C1 corresponding to the style data is obtained in the document specification layer of the specification library. Simultaneously, the document instance referencing the target document component becomes a specification instance referencing that specification component, for example, as shown... Figure 3 As shown, the document instance C1.1 that references the target document component C1 is transformed into a specification instance that references the specification component C1.

[0120] In some optional embodiments of this example, after publishing the document instance to the specification library, the specification component corresponding to the style data can also be obtained through the following steps:

[0121] Determine the document component to which the document instance belongs.

[0122] In this embodiment, based on the determination of the target document component referenced by the document instance according to the style data in step 51, the reference relationship between each document instance and each document component can be determined, and then the document component to which the document instance belongs can be determined based on the reference relationship. Furthermore, the document instance can be determined to belong to a document component by using the referenced list of the document component, thereby determining the document component to which each document instance belongs.

[0123] In response to the initial publication of a document instance, a specification component belonging to the document component and corresponding to the style data is created in the specification library.

[0124] In this embodiment, when publishing a document instance, the executing entity further determines whether its style data exists in the specification library. If it exists, it determines the document source and, according to the rule that specification components with the same style can be created repeatedly if they belong to different documents, and specification components with the same style cannot be created repeatedly if they belong to the same document, creates a specification component in the specification library that belongs to the document component and corresponds to the style data. This avoids the repeated creation of specification components, improves work efficiency, and reduces resource consumption.

[0125] Step 54: Change the document instance from referencing the target document component to referencing the specification component to obtain the specification instance.

[0126] In this embodiment, after publishing the document instance to the specification library in step 53 and obtaining the specification component corresponding to the style data, the document instance referencing the target document component after publication is changed to the specification instance referencing the specification component.

[0127] For example, such as Figure 6 As shown, before instance C1.1 is published, it is a document instance that references document component C1; after instance C1.1 is published, it is changed to a specification instance that references specification component C1.

[0128] In some optional embodiments of this example, the component processing method further includes Figure 11 The following steps are not shown in the image:

[0129] Determine the primary reference relationship between specification instances and specification components.

[0130] In this embodiment, a first reference relationship between a specification instance and a specification component is determined based on the style data of the specification instance and the style data of the specification component. That is, a first reference relationship is established between specification instances that match the style data of the specification component.

[0131] Based on the first reference relationship, determine the first list of referenced components in the specification.

[0132] In this embodiment, based on the aforementioned determined first reference relationship, the specification instances referencing the specification component can be identified, and these specification instances can be aggregated into the specification component. That is, the first reference relationship is aggregated into a first referenced list, which is then displayed in the specification component. Business personnel then... Figure 3 The specification component shown can know the specification instances that have a first reference relationship with the specification component. For example, the list of references of document 1 - specification component C1 includes instances C1.1, C1.2 and C1.3.

[0133] In response to an empty first referenced list, remove the canonical component.

[0134] In this embodiment, when the first referenced list is empty, the specification component is deleted. For example, when a business user deletes a specification instance C1.1 that has a reference relationship with the specification component C1 in the document canvas layer of the document library, the first referenced list of the corresponding specification component will be reduced by the deleted specification instance C1.1. When the first referenced list is empty, it indicates that there is no specification instance with the same style as the specification component in the document canvas layer. In other words, the user has not used this style of specification instance for creation, and the document specification component will be automatically deleted.

[0135] Step 55: Based on the style data, determine the target source component referenced by the specification component.

[0136] In this embodiment, the description of step 55 is the same as that of step 42, and will not be repeated here.

[0137] Furthermore, in some optional embodiments of this example, the component processing method further includes Figure 11 The following steps are not shown in the image:

[0138] Determine the second reference relationship between the target source component and the specification component.

[0139] In this embodiment, a second reference relationship between the target source component and the standard component is determined based on the style data of the standard component and the style data of the target source component. That is, a second reference relationship is established between standard components that match the style data of the target source component.

[0140] Based on the second reference relationship, determine the second list of references for the target source component.

[0141] In this embodiment, based on the aforementioned determined second reference relationship, the canonical components referencing the target source component can be identified, and these canonical components can be aggregated into the target component. That is, the second reference relationship is aggregated into a second referenced list, which is then displayed in the target source component. Business personnel can then... Figure 3 The source component shown can identify the specification components that have a second reference relationship with it. For example, the reference list of source component C* includes specification component C1 from document 1 and specification component C2 from document 2; the reference list of source component D* includes specification component D1 from document 3.

[0142] In response to an empty second referenced list, the target source component is removed.

[0143] In this embodiment, the target source component is deleted when the second referenced list is empty. For example, when a business user deletes document 1-specification component C1, which has a reference relationship with the target source component C*, in the document specification layer of the specification library, the corresponding target source component's second referenced list will decrease by the deleted specification component C1. When the second referenced list is empty, it indicates that there is no specification component with the same style as the target source component in the document specification layer. In other words, the user has not used this style of specification instance for creation. At this time, since the target source component will not be automatically deleted, it still exists and needs to be manually deleted.

[0144] Step 56: Combine multiple instances to obtain a combined instance, which includes document instances and / or specification instances.

[0145] In this embodiment, the executing entity can use a document container component to combine document instances or specification instances in the document canvas to obtain a combined instance. The combined instance can be obtained by combining multiple document instances, multiple specification instances, or a combination of specification instances and document instances. This application does not limit the scope of the application.

[0146] Step 57: Publish the composite instance to obtain the composite specification component.

[0147] In this embodiment, the executing entity can select the aforementioned instance combination for publication, and publish the instance combination to the specification library to obtain the combined specification component. Specifically, for the combined instance, the reference relationship between the combined instance and the combined document component is changed to a reference relationship with the combined specification component, thus obtaining the combined specification instance. For example, Figure 12 As shown, composite specification components, such as document 3 - composite specification component X; composite specification instances, such as instance X3.3.

[0148] In this embodiment, the composite specification components referenced by the composite specification instance are determined, and a third reference relationship is established between the composite specification instance and the composite specification component. Simultaneously, based on this third reference relationship, a third list of referenced composite specification components can be determined. When the third list of referenced components is empty, it indicates that the business personnel have not used this style of composite specification instance for creation, and the composite specification component will be automatically deleted. For example, the referenced list of document 3 - composite specification component X is instance X3.3. When the referenced list of document 3 - composite specification component X is empty, document 3 - composite specification component X will be automatically deleted, thereby reducing space overhead, releasing storage resources, and improving the efficiency of component updates and processing.

[0149] Step 58: Determine the composite source component referenced by the composite specification component.

[0150] In this embodiment, the source component referenced by the composite specification component is determined, and a fourth reference relationship is established between the composite specification component and the source component. Simultaneously, based on this fourth reference relationship, a fourth list of referenced components for the source component can be determined. When the fourth list of referenced components is empty, the source component needs to be manually deleted. For example, Figure 12 As shown, the reference list of the composite source component X* is document 3 - Composite Specification Component X. When the reference list of the composite source component X* is empty, the composite source component X* needs to be deleted to reduce space overhead, release storage resources, and improve the efficiency of component updates and processing.

[0151] In addition, such as Figure 13 As shown, combining source component C* and source component D* yields composite specification component X*. When creating document instance C2.3, if the style data is the same as that of the document component, it can be automatically referenced, establishing a bidirectional link between the document instance and the document component. When the style data of document component C2 changes, it can be synchronously pushed to each instance, such as instance C2.3, thereby updating the style data of the instance.

[0152] Furthermore, in this embodiment, when the style data in the combined source component is updated, it can be done by... Figure 14 The combined source component node shown allows you to select different documents or folders to synchronously push component updates, as well as choose to reject updates or ignore updates. This effectively avoids the impact of one component's update or iteration upgrade on the functionality and stability of other components, thereby achieving optimized component updates.

[0153] Within the specification library, a set of bidirectional links is established between a composite source component and its constituent source components. A composite source component references a source component within the composite, and this composite source component automatically appears in the source component's reference list. A composite source component can still be referenced by new composite source components, establishing bidirectional links. Furthermore, this composite instance creates and replaces the referenced composite specification component, becoming the composite specification instance itself. Additionally, if the instance composite contains a document instance, it checks whether a specification component with identical style data exists. If so, the document instance replaces the referenced specification component; otherwise, a document specification component is created, and the document instance replaces the reference.

[0154] It should be noted that the determination of style data and reference relationships involved in the publication and processing of combined instances in this embodiment is similar to the publication method of a single document instance (or a single document component) in the aforementioned embodiments, and will not be repeated here.

[0155] Further reference Figure 15 As an implementation of the component update method shown in the above figures, this disclosure provides an embodiment of a component update apparatus, which is similar to... Figure 2 Corresponding to the method embodiments shown, this component update device can be specifically applied to various electronic devices.

[0156] like Figure 15 As shown, the component includes a specification component, and the component update device includes:

[0157] The receiving module 1501 is configured to receive style editing operations on the specification components;

[0158] The first update module 1502 is configured to update the original style of the specification component based on the style editing operation to obtain the target style of the specification component;

[0159] Module 1503 is configured to retrieve specification instances of reference specification components;

[0160] The second update module 1504 is configured to update the specification instance based on the target style of the specification component.

[0161] In some optional embodiments of this example, the acquisition module is further configured as follows:

[0162] Get the first list of referenced components in the specification;

[0163] Based on the first cited list, determine the specification instance.

[0164] In some alternative embodiments of this example, the component further includes a source component, which is referenced by the canonical component;

[0165] The receiving module is configured as follows:

[0166] Receive style editing operations on the source component;

[0167] Based on the style editing operation, the original style of the source component is updated to obtain the target style of the source component;

[0168] Retrieve the canonical component that references the source component;

[0169] In response to the canonical component being set to receive style updates, the canonical component receives the target styles from the source component.

[0170] Specifically, based on style editing operations, the original style of the standardized component is updated to obtain the target style of the standardized component, including:

[0171] Based on the target style of the source component, the original style of the specification component is updated to obtain the target style of the specification component.

[0172] In some optional embodiments of this example, obtaining the canonical component that references the source component includes:

[0173] Get the second list of references to the source component;

[0174] Based on the second list of references, the specification components are identified.

[0175] In some optional embodiments of this example, the component updating device further includes:

[0176] The refuse-update module is configured to, in response to a specification component being set to refuse updates, delete the specification component and replace the specification instance that references the specification component with a document instance, where the document instance references the document component.

[0177] In some optional embodiments of this example, the component updating device further includes:

[0178] The ignore update module is configured to maintain the reference relationship between the canonical component and the source component in response to the canonical component being set to ignore updates.

[0179] Further reference Figure 16 As an implementation of the component processing methods shown in the above figures, this disclosure provides an embodiment of a component processing apparatus, which is similar to... Figure 8 Corresponding to the method embodiments shown, this component processing device can be specifically applied to various electronic devices.

[0180] like Figure 16 As shown, the component processing device includes:

[0181] Create module 1601, which is configured to create document instances and determine the style data of the document instances;

[0182] The publishing module 1602 is configured to publish document instances and obtain the specification components corresponding to the style data and the specification instances that reference the specification components;

[0183] Module 1603 is configured to determine the target source component referenced by the specification component based on style data.

[0184] In some alternative embodiments of this example, the publishing module is further configured as follows:

[0185] Based on the style data, determine the target document component referenced by the document instance;

[0186] Publish document instances by publishing the target document component.

[0187] In some optional embodiments of this example, determining the target document component referenced by the document instance based on style data includes:

[0188] In response to retrieving a candidate document component that matches the style data from the document library, the candidate document component is used as the target document component, and the association with the document instance is added to the reference list of the candidate document component;

[0189] In response to the failure to find a candidate document component that matches the style data from the document library, a target document component corresponding to the style data is created, and the association with the document instance is added to the reference list of the target document component.

[0190] In some alternative embodiments of this example, the publishing module is further configured as follows:

[0191] Publish the document instance to the specification library to obtain the specification component corresponding to the style data;

[0192] Change the document instance from referencing the target document component to referencing the specification component to obtain the specification instance.

[0193] In some optional embodiments of this example, the document instance is published to the specification library to obtain the specification component corresponding to the style data, including:

[0194] Determine the document component to which the document instance belongs;

[0195] In response to the initial publication of a document instance, a specification component belonging to the document component and corresponding to the style data is created in the specification library.

[0196] In some optional embodiments of this example, the component processing apparatus further includes:

[0197] The first reference relationship determination module is configured to determine the first reference relationship between specification instances and specification components;

[0198] The first referenced list determination module is configured to determine the first referenced list of specification components based on the first reference relationship;

[0199] The first deletion module is configured to delete the specification component in response to an empty first referenced list.

[0200] In some optional embodiments of this example, determining the target source component referenced by the specification component based on style data includes:

[0201] In response to obtaining a candidate source component that matches the style data from the specification library, the candidate source component is used as the target document component, and the association with the specification component is added to the reference list of the candidate source component;

[0202] In response to the failure to obtain a candidate source component that matches the style data from the specification library, a target source component corresponding to the style data is created, and the association with the specification component is added to the reference list of the target source component.

[0203] In some optional embodiments of this example, the component processing apparatus further includes:

[0204] The second reference relationship determination module is configured to determine the second reference relationship between the target source component and the specification component;

[0205] The second reference list determination module is configured to determine the second referenced list of the target source component based on the second reference relationship;

[0206] The second deletion module is configured to delete the target source component in response to an empty second referenced list.

[0207] In some optional embodiments of this example, the component processing apparatus further includes:

[0208] The composition module is configured to combine multiple instances to obtain a composite instance, where the multiple instances include document instances and / or specification instances;

[0209] The composite publishing module is configured to publish composite instances to obtain composite specification components;

[0210] The composite source component determination module is configured to determine the composite source components referenced by the composite specification components.

[0211] The acquisition, storage, and application of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0212] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0213] An electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the component update method or component processing method of the foregoing embodiments.

[0214] A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to perform the component update method or component processing method of the foregoing embodiments.

[0215] A computer program product includes a computer program that, when executed by a processor, implements the component update method or component processing method of the foregoing embodiments.

[0216] Figure 17A schematic block diagram of an example electronic device 1700 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0217] like Figure 17 As shown, device 1700 includes a computing unit 1701, which can perform various appropriate actions and processes according to a computer program stored in read-only memory (ROM) 1702 or a computer program loaded into random access memory (RAM) 1703 from storage unit 1708. The RAM 1703 may also store various programs and data required for the operation of device 1700. The computing unit 1701, ROM 1702, and RAM 1703 are interconnected via bus 1704. Input / output (I / O) interface 1705 is also connected to bus 1704.

[0218] Multiple components in device 1700 are connected to I / O interface 1705, including: input unit 1706, such as a keyboard, mouse, etc.; output unit 1707, such as various types of displays, speakers, etc.; storage unit 1708, such as a disk, optical disk, etc.; and communication unit 1709, such as a network card, modem, wireless transceiver, etc. Communication unit 1709 allows device 1700 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0219] The computing unit 1701 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 1701 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 1701 performs the various methods and processes described above, such as component update methods and component processing methods. For example, in some embodiments, the component update methods and component processing methods may be implemented as computer software programs tangibly contained in a machine-readable medium, such as storage unit 1708. In some embodiments, part or all of the computer program may be loaded and / or installed on device 1700 via ROM 1702 and / or communication unit 1709. When the computer program is loaded into RAM 1703 and executed by the computing unit 1701, one or more steps of the component update methods and component processing methods described above may be performed. Alternatively, in other embodiments, the computing unit 1701 may be configured to perform component update methods and component processing methods by any other suitable means (e.g., by means of firmware).

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

[0221] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

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

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

[0224] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0225] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0226] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

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

Claims

1. A component update method, wherein, The components include specification components and source components, and the method includes: Obtaining the canonical components that reference the source component includes: obtaining a second list of references to the source component, wherein the second list of references is used to record all canonical components that reference the source component, and aggregates and displays the reference relationships in the source component; and determining the canonical component based on the second list of references. In response to the specification component being set to receive style updates, the target style of the source component is received through the specification component; Based on the target style of the source component, the original style of the specification component is updated to obtain the target style of the specification component; Obtaining a specification instance that references the specification component includes: obtaining a first referenced list of the specification component; and determining the specification instance based on the first referenced list, wherein the first referenced list is used to record all specification instances that reference the specification component. Update the specification instance according to the target style of the specification component, so that the style data of the updated specification instance is the same as the target style of the specification component; The method further includes: In response to the specification component being set to refuse updates, the specification component is deleted, and the specification instance referencing the specification component is replaced with a document instance, wherein the document instance references the document component; In response to the specification component being set to ignore updates, the reference relationship between the specification component and the source component is maintained, and the source component is able to push updates to the specification component again; The method further includes: Based on the style editing operation of the source component, the original style of the source component is updated to obtain the target style of the source component.

2. A component processing method, comprising: Create a document instance and determine the style data for that document instance; Publish the document instance to obtain the specification component corresponding to the style data and the specification instance referencing the specification component; Based on the style data, determine the target source component referenced by the specification component; The method further includes: Determine the first reference relationship between the specification instance and the specification component; Based on the first reference relationship, a first reference list of the specification component is determined, wherein the first reference list is used to record all specification instances that reference the specification component; In response to the first referenced list being empty, the specification component is deleted; The method further includes: Determine the second reference relationship between the target source component and the specification component; Based on the second reference relationship, a second reference list of the target source component is determined, wherein the second reference list is used to record all specification components that reference the target source component, and the reference relationships are aggregated and displayed in the target source component; In response to the second referenced list being empty, the target source component is deleted.

3. The method according to claim 2, wherein, Publishing the document instance includes: Based on the style data, determine the target document component referenced by the document instance; The document instance is published by publishing the target document component.

4. The method according to claim 3, wherein, The step of determining the target document component referenced by the document instance based on the style data includes: In response to obtaining a candidate document component that matches the style data from the document library, the candidate document component is used as the target document component, and an association with the document instance is added to the reference list of the candidate document component; In response to the failure to obtain a candidate document component that matches the style data from the document library, a target document component corresponding to the style data is created, and an association with the document instance is added to the reference list of the target document component.

5. The method according to claim 4, wherein, The step of publishing the document instance to obtain the specification component corresponding to the style data and the specification instance referencing the specification component includes: The document instance is published to the specification library to obtain the specification component corresponding to the style data; The specification instance is obtained by changing the reference of the document instance from the reference of the target document component to the reference of the specification component.

6. The method according to claim 5, wherein, The step of publishing the document instance to the specification library to obtain the specification component corresponding to the style data includes: Determine the document component to which the document instance belongs; In response to the first publication of the document instance, a specification component belonging to the document component and corresponding to the style data is created in the specification library.

7. The method according to claim 2, wherein, The step of determining the target source component referenced by the specification component based on the style data includes: In response to obtaining a candidate source component that matches the style data from the specification library, the candidate source component is used as the target source component, and the association relationship with the specification component is added to the reference list of the candidate source component; In response to the failure to obtain a candidate source component that matches the style data from the specification library, a target source component corresponding to the style data is created, and the association with the specification component is added to the reference list of the target source component.

8. The method according to any one of claims 2-7, further comprising: Multiple instances are combined to obtain a combined instance, wherein the multiple instances include document instances and / or specification instances; The combined instance is published to obtain the combined specification component; Determine the combined source component referenced by the combined specification component.

9. A component updating device, wherein, The components include a specification component and a source component, and the apparatus includes: The first acquisition module is configured to acquire the specification components that reference the source component, including: acquiring a second reference list of the source component, wherein the second reference list is used to record all specification components that reference the source component and aggregate and display the reference relationships in the source component; and determining the specification component based on the second reference list. The first update module is configured to receive the target style of the source component through the specification component in response to the specification component being set to receive style updates. The second update module is configured to update the original style of the specification component according to the target style of the source component, so as to obtain the target style of the specification component; The second acquisition module is configured to acquire a specification instance that references the specification component; The third update module is configured to update the specification instance according to the target style of the specification component, so that the style data of the updated specification instance is the same as the target style of the specification component; The second acquisition module is further configured as follows: Obtain the first list of references for the specified component; Based on the first referenced list, the specification instance is determined, wherein the first referenced list is used to record all specification instances that reference the specification component; The device further includes: The refuse-update module is configured to, in response to the specification component being set to refuse update, delete the specification component and replace the specification instance referencing the specification component with a document instance, wherein the document instance references the document component; The ignore update module is configured to maintain the reference relationship between the specification component and the source component in response to the specification component being set to ignore updates, and the source component is able to push updates to the specification component again; The device further includes: The target style determination module is configured to update the original style of the source component based on the style editing operation of the source component, so as to obtain the target style of the source component.

10. A component processing apparatus, comprising: The creation module is configured to create document instances and determine the style data of the document instances; The publishing module is configured to publish the document instance to obtain the specification component corresponding to the style data and the specification instance referencing the specification component; The determination module is configured to determine the target source component referenced by the specification component based on the style data; The device further includes: The first reference relationship determination module is configured to determine the first reference relationship between the specification instance and the specification component; The first referenced list determination module is configured to determine a first referenced list of the specification component based on the first reference relationship, wherein the first referenced list is used to record all specification instances that reference the specification component; The first deletion module is configured to delete the specification component in response to the first referenced list being empty; The device further includes: The second reference relationship determination module is configured to determine the second reference relationship between the target source component and the specification component; The second reference list determination module is configured to determine a second reference list of the target source component based on the second reference relationship, wherein the second reference list is used to record all specification components that reference the target source component, and aggregate and display the reference relationship in the target source component; The second deletion module is configured to delete the target source component in response to the second referenced list being empty.

11. The apparatus according to claim 10, wherein, The publishing module is further configured as follows: Based on the style data, determine the target document component referenced by the document instance; The document instance is published by publishing the target document component.

12. The apparatus according to claim 11, wherein, The step of determining the target document component referenced by the document instance based on the style data includes: In response to obtaining a candidate document component that matches the style data from the document library, the candidate document component is used as the target document component, and an association with the document instance is added to the reference list of the candidate document component; In response to the failure to obtain a candidate document component that matches the style data from the document library, a target document component corresponding to the style data is created, and an association with the document instance is added to the reference list of the target document component.

13. The apparatus according to claim 12, wherein, The publishing module is further configured as follows: The document instance is published to the specification library to obtain the specification component corresponding to the style data; The specification instance is obtained by changing the reference of the document instance from the reference of the target document component to the reference of the specification component.

14. The apparatus according to claim 13, wherein, The step of publishing the document instance to the specification library to obtain the specification component corresponding to the style data includes: Determine the document component to which the document instance belongs; In response to the first publication of the document instance, a specification component belonging to the document component and corresponding to the style data is created in the specification library.

15. The apparatus according to claim 10, wherein, The step of determining the target source component referenced by the specification component based on the style data includes: In response to obtaining a candidate source component that matches the style data from the specification library, the candidate source component is used as the target source component, and the association relationship with the specification component is added to the reference list of the candidate source component; In response to the failure to obtain a candidate source component that matches the style data from the specification library, a target source component corresponding to the style data is created, and the association with the specification component is added to the reference list of the target source component.

16. The apparatus according to any one of claims 10-15, further comprising: The combination module is configured to combine multiple instances to obtain a combined instance, wherein the multiple instances include document instances and / or specification instances; The composite publishing module is configured to publish the composite instance to obtain the composite specification component; The combined source component determination module is configured to determine the combined source component referenced by the combined specification component.

17. An electronic device comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the component update method of claim 1 or the component processing method of any one of claims 2-8.

18. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to execute the component update method of claim 1 or the component processing method of any one of claims 2-8.

19. A computer program product comprising a computer program that, when executed by a processor, implements the component update method of claim 1 or the component processing method of any one of claims 2-8.

Images