CN116974577A

CN116974577A - Data processing method and device and electronic equipment

Info

Publication number: CN116974577A
Application number: CN202310956381.XA
Authority: CN
Inventors: 刘高
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2023-07-31
Filing date: 2023-07-31
Publication date: 2023-10-31

Abstract

The embodiment of the disclosure provides a data processing method, a data processing device and electronic equipment, wherein the method comprises the following steps: receiving a deleting operation of first metadata aiming at a target application, and determining whether a dependent object dependent on the first metadata exists or not; in response to determining that the dependent object exists, displaying release prompt information prompting release of the dependent relationship between the first metadata and the dependent object; and deleting the first metadata according to the detected release operation of the dependency relationship, which is executed based on the release prompt information. The lossless metadata deletion when the application is in the running state is realized. The metadata deletion realized by the method can not cause upper metadata collapse and can not generate irreversible faults of the application. In addition, the above manner supports lossless deletion of metadata, which helps reduce redundancy of application data packets.

Description

Data processing method and device and electronic equipment

Technical Field

The embodiment of the disclosure relates to the technical field of computers, in particular to a data processing method, a data processing device and electronic equipment.

Background

The low code development platform provides a user with a service that builds applications quickly without or with a small amount of code. An application built in a low code platform may have a plurality of metadata. Development and maintenance of the application can be achieved through editing operations on the metadata.

Disclosure of Invention

The embodiment of the disclosure provides a data processing method, a data processing device and electronic equipment.

In a first aspect, an embodiment of the present disclosure provides a data processing method, including: receiving a deleting operation of first metadata aiming at a target application, and determining whether a dependent object dependent on the first metadata exists or not; in response to determining that the dependent object exists, displaying release prompt information prompting release of the dependent relationship between the first metadata and the dependent object; and deleting the first metadata according to the detected release operation of the dependency relationship based on the release prompt information.

In a second aspect, embodiments of the present disclosure provide a data processing apparatus, the apparatus comprising: a determining unit configured to receive a deletion operation of first metadata for a target application, and determine whether a dependent object that depends on the first metadata exists; a display unit configured to display release prompt information prompting release of a dependency relationship between the first metadata and the dependent object in response to determination that the dependent object exists; and the deleting unit is used for deleting the first metadata according to the detected release operation of the dependency relationship received based on the release prompt information.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including: a processor and a memory; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored by the memory such that the at least one processor performs the above first aspect and the various possible data processing methods of the first aspect.

In a fourth aspect, embodiments of the present disclosure provide a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, implement the above first aspect and the various possible data processing methods of the first aspect.

In a fifth aspect, embodiments of the present disclosure provide a computer program product comprising a computer program which, when executed by a processor, implements the above first aspect and the various possible data processing methods of the first aspect.

According to the data processing method, the data processing device and the electronic equipment, whether a dependent object which depends on first metadata exists or not is determined by receiving the deleting operation of the first metadata aiming at target application; in response to determining that the dependent object exists, displaying release prompt information prompting release of the dependent relationship between the first metadata and the dependent object; and deleting the first metadata according to the detected release operation of the dependency relationship based on the release prompt information, so that when the metadata needs to be deleted, the dependency relationship between the metadata and the metadata depending on the metadata is released, and the metadata is deleted after the dependency relationship is released, thereby realizing lossless metadata deletion when the application is in a running state. The metadata deletion realized by the method can not cause upper metadata collapse and can not generate irreversible faults of the application. In addition, the above manner supports lossless deletion of metadata, which helps reduce redundancy of application data packets.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the solutions in the prior art, a brief description will be given below of the drawings that are needed in the embodiments or the description of the prior art, it being obvious that the drawings in the following description are some embodiments of the present disclosure, and that other drawings may be obtained from these drawings without inventive effort to a person of ordinary skill in the art.

FIG. 1 is a schematic flow chart diagram of some embodiments of a data processing method provided by the present disclosure;

FIG. 2 is a schematic flow chart diagram of further embodiments of a data processing method provided by the present disclosure;

FIG. 3 is a schematic illustration of a portion of the content of a metadata dependency;

FIG. 4 is another schematic diagram of a portion of content of metadata dependencies;

FIG. 5A is a schematic diagram of an application scenario;

FIG. 5B is a schematic illustration of an application scenario;

FIG. 6 is a block diagram of a data processing apparatus provided by the present disclosure;

fig. 7 is a schematic hardware structure of an electronic device according to an embodiment of the disclosure.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure, and it is apparent that the described embodiments are some embodiments of the present disclosure, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without inventive effort, based on the embodiments in this disclosure are intended to be within the scope of this disclosure.

In a low code platform, a user may complete application development through configuration operations, as well as more complex services through the low code platform.

The application program built in the low-code platform can have the dependency relationship between the metadata corresponding to the application program and other elements of the application program. After the low-code platform develops an application program, the user may have a need to delete part of metadata in the subsequent process of application iteration. To meet such a demand of the user, one scheme is to forcibly delete the metadata. If the metadata is forcibly deleted, upper metadata depending on the metadata may crash, causing irreversible failure of the application.

One solution is to not support deletion of these metadata, and to set an identification for indicating discarded metadata to be deleted. New metadata is created throughout the application lifecycle, replacing the discarded metadata with new metadata. And changes other elements that would otherwise depend on the discarded metadata to rely on new metadata. And then progressively update and replace the discarded metadata. However, the application data packets are more and more redundant due to the fact that metadata deletion is not supported, and the application packets are more and more complex and cannot be maintained due to the fact that the abandoned metadata cannot be cleaned timely.

In order to solve the adverse effect of the fact that deleting is not supported or forced to delete the metadata to be deleted in a low-code platform, the present disclosure provides a data processing method, when the metadata needs to be deleted, the dependency relationship of the metadata is released, and the metadata is deleted after the dependency relationship is released. The lossless metadata deletion of the application in the low-code platform in the running state is realized. The metadata deletion realized by the method can not cause upper metadata collapse and can not generate irreversible faults of the application. In addition, the disclosed manner supports lossless deletion of metadata, which helps reduce redundancy of application data packets.

Referring to FIG. 1, a schematic flow chart diagram of some embodiments of a data processing method provided by the present disclosure is shown. As shown in fig. 1, the method comprises the steps of:

s101: a delete operation is received for the first metadata of the target application, and a determination is made as to whether a dependent object is present that depends on the first metadata.

The execution subject of the data processing method in the present disclosure may be a terminal device or a server.

The target application may be any application. In some embodiments, the target application may be an application created on a low code platform.

The dependency is that an object may be any element that makes up the target application. In one example, the dependent object may be metadata of the target application. Metadata for a target application that is dependent on an object is described below. The target application created on the low code platform may correspond to a plurality of metadata. There may be a dependency relationship between the plurality of metadata. For example, B metadata refers to a metadata, there is a dependency relationship between B metadata and a metadata. Where B depends on A, which is relied upon by B. B may be regarded as upper layer metadata of a.

The plurality of metadata corresponding to the target application may include different types of metadata.

The first metadata includes one of the following:

object metadata, field metadata, operation metadata, page metadata, rights metadata, and application metadata.

When the dependent object is metadata of the target application, the dependent object may be one of object metadata, field metadata, operation metadata, page metadata, authority metadata, and application metadata.

The target application may include a plurality of object metadata. Each object metadata may include a plurality of field metadata. The operation metadata may correspond to one or more object metadata, or one or more field metadata.

The page metadata may be associated with the object metadata or may be associated with a plurality of operation metadata.

Wherein the object metadata may describe which data the system is to store the object of the target application, how the data is stored. The object type metadata includes identification, storage location information, and the like. The above object metadata may be, illustratively, descriptive data describing a person, a thing, a game, etc.

The field metadata may be an integral part of the constituent object metadata. One object metadata may correspond to a plurality of field metadata.

The object metadata may have a plurality of field metadata. The field metadata includes, but is not limited to, one or more of text, numbers, dates, mailboxes, options, boolean, rich text, files, formulas, summaries, associated objects, and the like.

Wherein, the field metadata of formulas, summaries, associated objects and the like in one object metadata can depend on other object metadata or on other field metadata in the object metadata.

The operation metadata describes operation data, including automatically generated system operations or user-defined operations. The operation metadata may be metadata that adds, deletes, changes, or searches for object metadata. Batch import, batch update, configuration of different business processes, etc. can be performed by manipulating the metadata.

Page metadata, which may be an application interface that is directly seen, directly operated by the user. The viewing of data, triggering of the flow, etc. may be performed in the page.

Rights metadata by which a user can configure a user role, different roles can be associated with different metadata types. After a preset role is granted to a user, the user can have permission to access a page accessible by the preset role; operating object data that is authorized to operate, and the like.

The field metadata may depend on the corresponding object metadata, and the operation metadata may depend on the corresponding object metadata and the field metadata; the page metadata may depend on the corresponding object metadata, field metadata, and operation metadata; rights metadata may depend on corresponding object metadata, field metadata, operation metadata, and page metadata.

It is understood that for each object metadata, the field metadata therein may be considered as a field metadata instance of the object metadata.

The field metadata instances of different object metadata may be different. The same object metadata or field metadata may be relied upon by different operational metadata.

The same object metadata, field metadata, or operation metadata may be relied upon by different pages.

The deletion operation here may be a deletion operation performed by the user on the first metadata.

After the execution body receives the deletion operation, it may be determined whether there is a dependent object that depends on the first metadata in various ways.

If it is determined that there is no dependent object that depends on the first metadata, the first metadata may be deleted directly.

S102: in response to determining that the dependent object exists, release prompt information prompting release of the dependency relationship between the first metadata and the dependent object is displayed.

In order to avoid the occurrence of a crash due to the irreversible failure of the target application caused by the direct deletion of the first metadata, after determining that the dependency object dependent on the first metadata exists in step S101, the first metadata may not be directly deleted, but the release prompt information may be displayed to prompt the user to release the dependency relationship first.

The release prompt may be displayed on the display interface of the execution body. Or sending the release prompt information to the terminal equipment used by the user sending the deleting operation.

S103: and deleting the first metadata according to the detected release operation of the dependency relationship based on the release prompt information.

As an implementation manner, after receiving the release prompt information, the user may perform a release operation for releasing the dependency relationship between the first metadata and the dependent object according to the release prompt information.

The electronic device storing the dependency relationship between the first metadata and the dependent object may release the dependency relationship after receiving the release operation. The above described releasing operation may be, for example, a deleting operation to delete the dependent object or a replacing operation to set other dependent metadata for replacing the first metadata for the dependent object. The above-described operation of releasing the dependency relationship may be determined by the user as needed.

The execution body may detect whether a dependency relationship between the first metadata and the dependent object is released. The execution body may delete the first metadata after detecting that the dependency relationship between the first metadata and the dependent object is released.

In this embodiment, a deletion operation of first metadata for a target application is received, and whether a dependent object dependent on the first metadata exists is determined; in response to determining that the dependent object exists, displaying release prompt information prompting release of the dependency relationship between the first metadata and the dependent object; and deleting the first metadata according to the received release operation for releasing the dependency relationship, which is executed by the release prompt information. When deleting the first metadata, the dependency relationship between the first metadata and the dependent objects depending on the first metadata is firstly released, so that the first metadata is deleted after the dependency relationship between the first metadata and all the dependent objects depending on the first metadata is already released, namely, after the first metadata is deleted, the application program does not have the dependent objects depending on the first metadata, therefore, after the first metadata is deleted, the application program can run without any obstacle, thereby realizing lossless metadata deletion when the application program is in a running state, and the metadata deletion realized by the mode does not cause the dependent objects depending on the deleted metadata to crash and also does not generate irreversible faults of the application program. In addition, the above manner helps to reduce redundancy of application data packets by lossless deletion of metadata.

Referring to FIG. 2, a schematic flow chart diagram of further embodiments of the data processing method provided by the present disclosure is shown. As shown in fig. 2, the method comprises the steps of:

s201: and receiving a deleting operation of the first metadata aiming at the target application, and determining whether a dependent object dependent on the first metadata exists according to the metadata dependency relationship of the target application.

The execution main body of the data processing method can be user terminal equipment or a server.

And storing the dependent object and the dependent metadata according to the metadata dependency relationship.

Some of the relevant descriptions of step S201 may refer to the description of step S101 of the embodiment shown in fig. 1.

As an implementation manner, the step S201 includes the following steps:

first, a metadata list of a target application is displayed to a user, the metadata list including a plurality of metadata.

In this embodiment, in order to facilitate browsing and management of metadata by a user, a metadata list may be displayed to the user according to the user's operation.

The metadata list may include a plurality of metadata of the target application.

In one example, the metadata list may be divided into a plurality of sub-metadata lists according to metadata types. The user may perform a triggering operation on each sub-metadata list, thereby displaying a plurality of metadata in the sub-metadata list.

In the displayed metadata list, a plurality of identifications respectively corresponding to the metadata may be displayed.

Next, a deletion operation performed by the user on the first metadata in the metadata list is received.

In some embodiments, a user may perform a selection operation on one or more metadata from among the displayed plurality of metadata, thereby selecting first metadata from among the plurality of metadata.

After the first metadata is selected, the user may perform a delete operation on the first metadata.

In one example, after the user selects the first metadata, the user performs a triggering operation on a deletion control displayed in the display interface.

In one example, after the user performs a selection operation on the first metadata, a deletion selection item for deleting the metadata may be displayed. The user may perform a triggering operation on the deletion selection item, thereby completing a deletion operation of deleting the first metadata.

In some embodiments, for each metadata identification, a corresponding delete option may be displayed in a metadata list displayed to the user. In these embodiments, the user may perform the triggering operation on the deletion option corresponding to any metadata, which is the first metadata.

In these embodiments, by displaying a metadata list of the target application to the user, the user can select the first metadata from the metadata list to perform a deletion operation on the first metadata. Because the metadata list is displayed to the user, the user selects the first metadata in the metadata list, and the deleting operation is performed on the first metadata, the metadata management is facilitated, and the efficiency of editing the metadata by the user is improved.

The metadata dependency relationship includes a dependent object (e.g., metadata) and dependent metadata. The metadata dependencies of the applications may be centrally managed, e.g., the metadata dependencies of the applications are maintained in a metadata dependency table. Through centralized management of the dependency relationships of the multiple metadata corresponding to the target application, the follow-up operation on the dependency relationships of the metadata is facilitated.

Illustratively, according to metadata dependencies, for each dependent object, the dependent object may be stored in association with the plurality of dependent metadata on which it depends, respectively.

Illustratively, according to the metadata dependency described above, for each metadata, the metadata and one or more dependent objects that depend on the metadata may be stored in association.

Taking the dependency object as metadata, the dependency relationship of the metadata is stored in a metadata dependency relationship table as an example, please refer to fig. 3, which shows a part of contents in one metadata dependency relationship table. As shown in fig. 3, the metadata dependency table may include fields: "dependent metadata type", "identified by dependent metadata", "dependent metadata type", "dependent metadata identification" and "dependent metadata extension information". In the metadata dependency table, contents corresponding to the fields may be described. As in fig. 3, the content corresponding to the field "dependent metadata type" is "object"; the content corresponding to the field 'depended metadata identification' is 'object 2'; the content corresponding to the field 'dependent metadata type' is a 'page'; the content corresponding to the field 'relying on metadata identification' is 'page 4'; the content corresponding to the field "dependent metadata extension information" is "table 2". The partial metadata dependency table described above may represent "table 2 dependency object 2 in page 4".

A dependent object may depend on multiple dependent metadata. Illustratively, the page 4 (dependent object) described above may rely on the operation metadata 5 in addition to the object metadata 2. Fig. 4 shows part of the content in the metadata dependency table. In the partial content, the content corresponding to the field "dependent metadata type" is "object"; the content corresponding to the field 'depended metadata identification' is 'object 2'; the content corresponding to the field 'dependent metadata type' is a 'page'; the content corresponding to the field "dependent metadata identification" is "page 4", and the content corresponding to the field "dependent metadata extension information" is "table 2". The partial metadata dependency may represent "table 2 dependency object 2" in page 4. The above partial metadata dependency relationship may represent "button 3 dependency operation 5" in page 4.

In this way, the associative storage of the metadata dependency relationship can find the dependent metadata on which any metadata depends. Dependent metadata that depends on any of the dependent metadata may also be looked up.

The metadata dependencies may be created after the target application is built.

In some embodiments, the data processing method further includes:

and updating the metadata dependency relationship of the target application according to the editing operation of the user on the metadata dependency relationship of the target application.

In these embodiments, the user performs editing operations on the metadata, including editing operations such as modifying the identification of the metadata, deleting the metadata, and the like.

Editing operations of the metadata dependency relationship include adding dependent metadata, deleting dependent metadata or modifying dependent metadata, and the like.

The dependency relationship of the metadata may be updated each time the user edits the metadata dependency relationship.

After the user performs editing operation on the metadata dependency relationship, the metadata dependency relationship can be updated, so that the latest dependency relationship in the metadata dependency relationship is ensured, and the irreparable fault of the target application, which is caused by that the dependency relationship is not released when the metadata is deleted under the condition that the dependency relationship is not updated, is avoided, and the irreparable fault can cause damage to the application program in running or can not be normally displayed.

S202: in response to determining that the dependent object exists, release prompt information prompting release of the dependency relationship between the first metadata and the dependent object is displayed.

If it is determined that there is a dependent object dependent on the first metadata based on the metadata dependency relationship, a release hint may be displayed. Meanwhile, the first metadata deletion failure can be prompted in the release prompt information.

If there are a plurality of dependent objects that depend on the first metadata, information of the plurality of dependent objects may be displayed on the release instruction information display interface.

S203: and displaying a release page according to the received trigger operation executed on the release operation control in the release prompt information.

For each dependent object, the release prompt information may display the release operation control corresponding to the dependent object. The undo control may be associated with a link corresponding to a reference location in the dependent object that references the first metadata.

Referring to fig. 5A, an application scenario is shown. As shown in fig. 5A, a metadata list of the target application may be displayed in a related page of the target application. The target application may include different types of metadata. The respective lists of different types of metadata may be displayed separately. As shown in fig. 5A, a metadata list of object types is displayed. The object name and the operation options are included in the metadata list of the object type. The operation options may include an edit operation item and a delete operation item. Only the delete operation item is shown in fig. 5A. The user can perform a trigger operation on the deletion operation item corresponding to the object 1, thereby performing a deletion operation of deleting the object 1. Object 1 here may be any object type metadata. Object 1 may be considered as first metadata.

Fig. 5B is a schematic view of an application scenario. Upon detecting that the user performs a deletion operation of the metadata object 1, the above-described execution body may find a dependent object that depends on the metadata object 1 in the metadata dependency relationship. It is determined from the search result that the metadata object 2 and the metadata operation B are dependent objects that depend on the metadata object 1, that is, the metadata object 1 is dependent metadata, and the metadata object 2 and the metadata operation B are dependent objects. Referring to fig. 5B, the execution body may display release prompt 501. The release hint information 501 includes hint information 502 "deletion failure, please release the dependency relationship" for prompting deletion failure. In addition, the release hint information 501 may also display information of the dependent object that depends on the metadata object 1, for example, metadata "object 2" that depends on the metadata object 1, and "operation B", and specific location information of the metadata object 1 is referred to, for example, in fig. 5B, where the metadata "object 2" refers to the location of the object 1 as "field a"; "operation B" refers to the position of object 1 as "creation node". In addition, a release operation control such as "go to modification" shown in fig. 5B may be displayed in the release prompt message. Taking metadata object 2 as an example, a user may trigger a release operation control corresponding to metadata object 2, thereby displaying a release page of metadata object 2. In the release page of the metadata object 2, the user can perform a release operation to release the dependency of the metadata object 2 on the metadata object 1.

The user may execute a trigger operation on the release operation control of any one of the dependent objects, so as to display a release page for releasing the dependent relationship. The dismissal page may include details of the dependent object.

In some implementations, the data processing method further includes: in the displayed release page, the target position of the dependent first metadata in the dependent object is highlighted.

In some application scenarios, the highlighting the target location of the dependent object that depends on the first metadata includes setting a background color of the target location to a display mode different from other background colors.

In some application scenarios, highlighting the target location includes: positioning the cursor to the target position. When the release page is displayed according to a user performing a trigger operation on the release operation control, a cursor in the release page may be positioned to a target position in the dependent object that depends on the first metadata.

Illustratively, the first metadata is object metadata 1, the dependent object is object metadata 2, and field a of object metadata 2 references object metadata 1, i.e., object metadata 2 depends on object metadata 1. After the user performs the deletion operation of deleting the object metadata 1, release hint information that hint to release the dependency relationship between the object metadata 2 and the object metadata 1 may be displayed to the user. The release prompt message includes an identification of the object source code data 2. The object metadata 2 refers to the location (i.e., field a) of the object metadata 1. The release prompt may further include a release operation control. After the user performs the triggering operation on the release operation control, the execution body may detect the triggering operation performed on the release operation control by the user, so as to enter a metadata page corresponding to the object metadata 2, that is, a release page. In which the cursor can be positioned to the field metadata a described above.

In these embodiments, the user may be enabled to quickly find the target location by highlighting the target location.

S204: a dismissal operation performed on the dependency at the dismissal page is received.

The user may perform the release operation in the release page. Such release operations include, but are not limited to: a delete operation to delete the dependent object; the metadata on which the dependent object depends is modified, i.e. the first metadata on which it depends is modified to other metadata.

When the release prompt information comprises a plurality of dependent objects, a user can enter a release page corresponding to each dependent object through the release operation control of each dependent object. And releasing the dependency relationship between the dependent object and the first metadata in the release page.

S205: and deleting the first metadata according to the detected release operation of the dependency relationship based on the release prompt information.

The execution body may delete the first metadata after detecting that the dependency relationship between each of the dependent objects and the first metadata is released.

Compared with the embodiment shown in fig. 2, in the embodiment, metadata dependency relationship is used for associating and storing the dependent metadata and the dependent metadata, a release operation control is provided in release prompt information, a release page is displayed through triggering operation of a user on the release operation control, and a user can release implementation content of the dependency relationship between the first metadata and the dependent object in the release page. Therefore, unified management of multiple dependency relationships among metadata related to the target application is achieved, efficiency of editing the metadata according to the dependency relationships is improved, and convenience is brought to a user for deleting the metadata.

In some alternative implementations of the data processing method shown in fig. 1 and the data processing method shown in fig. 2, the step S103 shown in fig. 1 and the step S205 shown in fig. 2 described above include the following sub-steps:

first, after detecting a release operation, it is determined whether there are other dependent objects that depend on the first metadata.

Second, the first metadata is deleted in response to determining that no other dependent objects are present.

The other dependent object may be any metadata that depends on the first metadata. Other dependent objects may overlap with the dependent objects described above.

In these implementations, after detecting that the dependency relationship between the first metadata and the dependent object is released, it may be detected whether there is another dependent object that depends on the first metadata, and if there is no other dependent object, the first metadata may be deleted.

In the above implementation manner, by detecting whether other dependent objects dependent on the first metadata exist, the occurrence of an unmodified fault of the target application program due to the fact that the metadata dependent relationships dependent on the first metadata are not completely released is avoided.

Fig. 6 is a block diagram of a data processing apparatus according to an embodiment of the present disclosure, corresponding to the data processing method of the embodiment shown in fig. 1. For ease of illustration, only portions relevant to embodiments of the present disclosure are shown. Referring to fig. 6, the apparatus 60 includes: a determination unit 601, a display unit 602, and a deletion unit 603. Wherein, the liquid crystal display device comprises a liquid crystal display device,

A determining unit 601, configured to receive a deletion operation of first metadata for a target application, and determine whether a dependent object that depends on the first metadata exists;

a display unit 602 configured to display release hint information that hint to release a dependency relationship between the first metadata and the dependent object, in response to determining that the dependent object exists;

the deleting unit 603 is configured to delete the first metadata according to the detected release operation of the dependency relationship performed based on the release prompt information.

In one embodiment of the present disclosure, the determining unit 601 is further configured to:

according to the metadata dependency relationship of the target application, whether a dependent object which depends on the first metadata exists or not is determined.

In one embodiment of the present disclosure, the apparatus 60 further comprises an updating unit (not shown in the figures). The updating unit is used for:

In one embodiment of the present disclosure, the release hint information includes a release operation control for releasing the dependency; the deleting unit 603 is further configured to:

displaying a release page according to the received trigger operation executed on the release operation control in the release prompt information;

A dismissal operation performed on the dependency at the dismissal page is received.

In one embodiment of the present disclosure, the deleting unit 603 is further configured to:

in the displayed release page, the target position of the dependent first metadata in the dependent object is highlighted.

displaying a metadata list of the target application, the metadata list including a plurality of metadata;

a delete operation performed on the first metadata in the metadata list is received.

upon detecting the dismissal operation, determining whether there are other dependent objects that depend on the first metadata;

the first metadata is deleted in response to determining that no other dependent objects are present.

In one embodiment of the present disclosure, the first metadata and the second metadata include one of:

In order to achieve the above embodiments, the embodiments of the present disclosure further provide an electronic device.

Referring to fig. 7, there is shown a schematic diagram of an electronic device 700 suitable for use in implementing embodiments of the present disclosure, which electronic device 700 may be a terminal device or a server. The terminal device may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a personal digital assistant (Personal Digital Assistant, PDA for short), a tablet (Portable Android Device, PAD for short), a portable multimedia player (Portable Media Player, PMP for short), an in-vehicle terminal (e.g., an in-vehicle navigation terminal), and the like, and a fixed terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 7 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.

As shown in fig. 7, the electronic apparatus 700 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 701 that may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage device 708 into a random access Memory (Random Access Memory, RAM) 703. In the RAM 703, various programs and data required for the operation of the electronic device 700 are also stored. The processing device 701, the ROM702, and the RAM 703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

In general, the following devices may be connected to the I/O interface 705: input devices 706 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 707 including, for example, a liquid crystal display (Liquid Crystal Display, LCD for short), a speaker, a vibrator, and the like; storage 708 including, for example, magnetic tape, hard disk, etc.; and a communication device 709. The communication means 709 may allow the electronic device 700 to communicate wirelessly or by wire with other devices to exchange data. While fig. 7 shows an electronic device 700 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communication device 709, or installed from storage 708, or installed from ROM 702. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing device 701.

It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program (computer-executable instructions) for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

The computer-readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above-described embodiments.

Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a local area network (Local Area Network, LAN for short) or a wide area network (Wide Area Network, WAN for short), or it may be connected to an external computer (e.g., connected via the internet using an internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. Wherein the name of the unit does not constitute a limitation of the unit itself in some cases, for example, the determination unit may also be described as "a unit that receives a deletion operation of the first metadata for the target application, determines whether there is a dependent object that depends on the first metadata".

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).

Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.

Claims

1. A data processing method, comprising:

receiving a deleting operation of first metadata aiming at a target application, and determining whether a dependent object dependent on the first metadata exists or not;

in response to determining that the dependent object exists, displaying release prompt information for prompting release of the dependent relationship between the first metadata and the dependent object;

and deleting the first metadata according to the detected release operation of the dependency relationship, which is executed based on the release prompt information.

2. The method of claim 1, wherein the determining whether there is a dependent object that depends on the first metadata comprises:

and determining whether a dependent object which depends on the first metadata exists according to the metadata dependency relationship of the target application.

3. The method according to claim 2, wherein the method further comprises:

4. The method of claim 1, wherein the release hint information includes a release operation control to release the dependency; the method further comprises the steps of:

a release operation performed on the dependency on the release page is received.

5. The method according to claim 4, wherein the method further comprises:

and highlighting the target position depending on the first metadata in the dependent object in the displayed release page.

6. The method of claim 1, wherein the receiving the delete operation performed on the first metadata of the target application comprises:

displaying a metadata list of the target application, wherein the metadata list comprises a plurality of metadata;

7. The method of claim 1, wherein the deleting the first metadata according to the detected release operation of the dependency relationship performed based on the release hint information comprises:

8. The method of any of claims 1-7, wherein the first metadata and dependent objects comprise one of:

9. A data processing apparatus comprising:

a determining unit configured to receive a deletion operation of first metadata for a target application, and determine whether a dependent object that depends on the first metadata exists;

a display unit configured to display release prompt information prompting release of a dependency relationship between the first metadata and the dependent object in response to determination that the dependent object exists;

and the deleting unit is used for deleting the first metadata according to the detected release operation of the dependency relationship received based on the release prompt information.

10. An electronic device, comprising: a processor and a memory;

the memory stores computer-executable instructions;

The processor executing computer-executable instructions stored in the memory, causing the processor to perform the data processing method of any one of claims 1 to 8.

11. A computer-readable storage medium, in which computer-executable instructions are stored which, when executed by a processor, implement the data processing method according to any one of claims 1 to 8.