CN114564206A - Data non-empty checking method, device, equipment and readable storage medium - Google Patents
Data non-empty checking method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN114564206A CN114564206A CN202210212907.9A CN202210212907A CN114564206A CN 114564206 A CN114564206 A CN 114564206A CN 202210212907 A CN202210212907 A CN 202210212907A CN 114564206 A CN114564206 A CN 114564206A
- Authority
- CN
- China
- Prior art keywords
- information
- field name
- empty
- annotation
- attribute corresponding
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/43—Checking; Contextual analysis
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a data non-empty checking method, a device, equipment and a readable storage medium, which relate to the technical field of computers and comprise the steps of obtaining first information, wherein the first information comprises at least one parameter entity information filled in a terminal, and the parameter entity information comprises at least two field names and a value attribute corresponding to the field names; traversing all the annotations of the field names according to a first preset annotation to obtain the existence state of the first preset annotation, wherein the existence state comprises existence or nonexistence; when the existing state exists, the existing state triggers and calls a non-empty check interceptor to perform non-empty check on the first information, and the invention realizes the non-empty check in a mode of interceptor plus annotation, improves the development efficiency, reduces the code amount, and distinguishes scenes according to the condition of parameter values, thereby realizing a flexible non-empty check mode.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a data non-empty checking method, device and equipment and a readable storage medium.
Background
Spring grouping checking technology: firstly defining a plurality of grouping interfaces, then adding NotNull notes on fields needing non-empty check, specifying which groups the fields can not be empty through group parameters, finally setting @ Validated notes in a method signature using the parameters, and specifying which group the current interface belongs to through the parameters, wherein the non-empty check method can not realize the purpose of scene check during code development.
Disclosure of Invention
The present invention is directed to a method, an apparatus, a device and a readable storage medium for non-empty data check, so as to solve the above problems. In order to achieve the purpose, the technical scheme adopted by the invention is as follows:
in a first aspect, the present application provides a data non-empty checking method, including: acquiring first information, wherein the first information comprises filled at least one parameter entity information, and the parameter entity information comprises at least one field name and a value attribute corresponding to the field name; traversing all the annotations of the field names according to a first preset annotation to obtain the existence state of the first preset annotation, wherein the existence state comprises existence or nonexistence; and when the existence state is existence, the existence state triggers and calls a non-null check interceptor to perform non-null check on the first information.
Further, the triggering of the presence state calls a non-null check interceptor to perform non-null check on the first information, including: calculating to obtain second information according to the first information, wherein the second information comprises a first check scene; traversing the value attribute corresponding to each field name in the first information, and respectively performing non-empty check based on the second information to obtain third information, wherein the third information comprises a failed field name, and the failed field name is the field name for which the check fails.
Further, the calculating according to the first information obtains second information, where the second information includes a first check scenario, and includes: acquiring and analyzing a first preset scene calculation function to obtain a function variable set, wherein the function variable set comprises at least one parameter name; extracting fourth information from the first information according to the parameter name, wherein the fourth information comprises a value attribute corresponding to the parameter name; and calculating to obtain a first verification scene according to the first preset scene calculation function and the fourth information.
Further, traversing the value attribute corresponding to each field name in the first information, and performing non-empty check based on the second information to obtain at least one failed field name, includes: judging the annotation content of the field name, and if the field name is not annotated by the first preset annotation, judging the annotation content of the next field name; if the field name is annotated by the first preset annotation, judging whether the value attribute corresponding to the field name is empty, and if not, judging the annotation content of the next field name; if the value attribute corresponding to the field name is null, judging whether the value attribute corresponding to the annotation of the first preset annotation is null, and if the value attribute corresponding to the annotation of the first preset annotation is null, recording the field name as a failed field name; if the value attribute corresponding to the first preset annotation note is not empty, judging whether the value attribute corresponding to the first preset annotation note contains a first verification scene, and if the value attribute corresponding to the first preset annotation note contains the first verification scene, recording the field name as a failed field name.
Further, the recording the field name as a failed field name further includes: and if the failed field name exists, sending a first control command and re-acquiring the first information, wherein the first control command comprises a command for controlling a display to display that the failed field name cannot be null.
In a second aspect, the present application further provides a non-empty data checking apparatus, including: the device comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring first information which comprises at least one filled parameter entity information, and the parameter entity information comprises at least one field name and a value attribute corresponding to the field name; the first identification unit is used for traversing all the annotations of the field names according to a first preset annotation to obtain the existence state of the first preset annotation, and the existence state comprises existence or nonexistence; and the trigger execution unit is used for triggering and calling a non-empty check interceptor to carry out non-empty check on the first information in the presence state.
Further, the trigger execution unit includes: the first calculation unit is used for calculating second information according to the first information, and the second information comprises a first check scene; and the checking unit is used for traversing the value attribute corresponding to each field name in the first information and respectively performing non-empty checking on the basis of the second information to obtain third information, wherein the third information comprises a failed field name, and the failed field name is the field name which is failed in checking.
Further, the first calculation unit includes: the analysis unit is used for acquiring and analyzing a first preset scene calculation function to obtain a function variable set, wherein the function variable set comprises at least one parameter name; the extracting unit is used for extracting fourth information from the first information according to the parameter name, and the fourth information comprises a value attribute corresponding to the parameter name; and the second calculating unit is used for calculating to obtain a first check scene according to the first preset scene calculating function and the fourth information.
Further, the verification unit includes: the first logic unit is used for judging the annotation content of the field name, and judging the annotation content of the next field name if the field name is not annotated by the first preset annotation; a second logic unit, configured to determine whether a value attribute corresponding to the field name is null if the field name is annotated by the first preset annotation, and determine annotation content of a next field name if the value attribute corresponding to the field name is not null; a third logic unit, configured to determine whether the value attribute corresponding to the comment of the first preset comment is null if the value attribute corresponding to the field name is null, and mark the field name as a failed field name if the value attribute corresponding to the comment of the first preset comment is null; and the fourth logic unit is configured to determine whether the value attribute corresponding to the first preset annotation includes a first check scenario if the value attribute corresponding to the first preset annotation is not empty, and mark the field name as a failed field name if the value attribute corresponding to the first preset annotation includes the first check scenario.
Further, the verification unit further includes: and the sixth logic unit is used for sending a first control command and acquiring the first information again if the failing field name exists, wherein the first control command comprises a command for controlling the display to display that the failing field name cannot be null.
In a third aspect, the present application further provides a data non-empty verification device, including:
a memory for storing a computer program;
a processor for implementing the steps of the data non-null check method when executing the computer program.
In a fourth aspect, the present application further provides a readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps of the data-based non-empty check method described above.
The invention has the beneficial effects that:
the invention realizes non-empty check by the interceptor and annotation mode, improves the development efficiency, reduces the code amount, distinguishes scenes according to the condition of parameter values and realizes a flexible non-empty check mode.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the embodiments of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a schematic flow chart of a data non-empty check method described in embodiment 1 of the present invention;
fig. 2 is a schematic structural diagram of a data non-empty verification apparatus according to embodiment 2 of the present invention;
fig. 3 is a schematic structural diagram of a data non-empty verification apparatus in embodiment 3 of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Example 1:
the embodiment provides a data non-null checking method.
Referring to fig. 1, the method is shown to include step S100, step S200 and step S300.
S100, first information is obtained, wherein the first information comprises at least one filled parameter entity information, and the parameter entity information comprises at least one field name and a value attribute corresponding to the field name.
It should be noted that, in the present application, the first information source may be information transmitted by a terminal through an interface, or information transmitted by another server through an interface. The terminal may be a mobile phone terminal, a personal computer terminal, or other counter service terminals, and no specific limitation is made in this application.
S200, traversing the annotations of all the field names according to the first preset annotation to obtain the existence state of the first preset annotation, wherein the existence state comprises existence or nonexistence.
S300, when the existence state is the existence state, the existence state triggers and calls a non-null check interceptor to carry out non-null check on the first information.
In the method, the starting of the verification is started through the existence state of the first preset annotation, and compared with the situation that the prior art needs to rely on the interface used according to the parameter object, the method is more convenient and faster in the code development stage, and the code amount is effectively reduced.
It should be noted that, in the present method, the sceneableNotnull is used as the first preset annotation. And the non-empty check interceptors may be implemented by springAOP.
Further, in some specific embodiments, step S300 includes step S310 and step S320.
And S310, calculating to obtain second information according to the first information, wherein the second information comprises a first check scene.
S320, traversing the value attribute corresponding to each field name in the first information, and respectively performing non-null check based on the second information to obtain third information, wherein the third information comprises a field name which fails to pass, and the field name which fails to pass the check is the field name which fails to pass the check.
In the application, after the SceneAbletoNull is checked and labeled, a first verification scene is calculated through a first verification scene calculation method defined on an interface, so that the purpose of distinguishing the verification scenes according to the condition of parameter values is achieved.
In some specific embodiments, step S310 includes step S311, step S312, and step S313 to implement the first verification scenario verification.
S311, obtaining and analyzing a first preset scene calculation function to obtain a function variable set, wherein the function variable set comprises at least one parameter name;
s312, extracting fourth information from the first information according to the parameter names, wherein the fourth information comprises value attributes corresponding to the parameter names;
and S313, calculating according to the first preset scene calculation function and the third information to obtain a first check scene.
For convenience of explanation, in the present application, for example, a getScene method is defined first, and the definition of the method is common knowledge in the field and is not described in detail in the present application.
Within the defined getScene method, the specific function is: { if (age! & & age > (18) } return "adult"; else return "minor", where age is the parameter name in the foregoing, and the current scene may be calculated by calling the value attribute corresponding to the age in the getScene method. Meanwhile, it should be noted that, for those skilled in the art, multiple verification scenarios may be set on the same code layer to fulfill the verification requirement of the data.
In some specific embodiments, the step S320 includes the step S321, the step S322, the step S313 and the step S314 to verify the data with the first verification scenario.
S321, judging the annotation content of the field name, and if the field name is not annotated by the first preset annotation, judging the annotation content of the next field name.
S322, if the field name is annotated by the first preset annotation, judging whether the value attribute corresponding to the field name is null, and if the value attribute corresponding to the field name is not null, judging the annotation content of the next field name.
And S323, if the value attribute corresponding to the field name is null, judging whether the value attribute corresponding to the annotation of the first preset annotation is null, and if the value attribute corresponding to the annotation of the first preset annotation is null, recording the field name as a failed field name. And S324, if the value attribute corresponding to the first preset annotation note is not empty, judging whether the value attribute corresponding to the first preset annotation note contains a first verification scene, and if the value attribute corresponding to the first preset annotation note contains the first verification scene, marking the field name as a failed field name.
In the method, the name of each field is labeled by the SceneAbletoNull through traversal, wherein the field name labeled by the SceneAbletoNull needs to be checked in a non-null way, then whether the SceneAbletoNull is null or not is judged, if the SceneAbletoNull is null, the fact that the SceneAbletoNull needs to be checked in a non-null way no matter what checking scene is indicated, and when the SceneAbleNotNull has a specific checking scene, whether the checking scene in the SceneAbleNotNull is contained in the second information is called. A non-null check is hit if the value attribute of the field name is null and the check scenario is within the second information. Such as: ID @ SceneAbleNotNull ("adult", "chinese"), which is the current scene, needs to be examined for adults or chinese.
In the step, when the non-empty checking is carried out on a plurality of scenes simultaneously by the method, and the non-empty checking is carried out by the method, the development amount of codes can be effectively reduced.
Meanwhile, in some specific embodiments, step S329 is further included in step S320.
S329, if the failing field name exists, sending a first control command and re-acquiring the first information, wherein the first control command comprises a command for controlling the display to display that the failing field name cannot be null.
In the method, for the field names which are verified to be empty, the terminal user is prompted to fill in relevant information, and data entry is completed.
Example 2:
as shown in fig. 2, the present embodiment provides a data non-empty verification apparatus, which includes:
the first acquiring unit 1 is configured to acquire first information, where the first information includes at least one filled parameter entity information, and the parameter entity information includes at least one field name and a value attribute corresponding to the field name.
The first identification unit 2 is configured to traverse annotations of all field names according to the first preset annotation to obtain a presence state of the first preset annotation, where the presence state includes presence or absence.
And the trigger execution unit 3 is used for triggering and calling the non-null check interceptor to perform non-null check on the first information in the presence state.
In some specific embodiments, the trigger execution unit 3 includes:
the first calculating unit 31 is configured to calculate second information according to the first information, where the second information includes the first verification scenario.
And the checking unit 32 is configured to traverse the value attribute corresponding to each field name in the first information, and perform non-null checking on the basis of the second information to obtain third information, where the third information includes a field name that fails to pass the checking, and the field name that fails to pass the checking is the field name that fails to pass the checking.
In some specific embodiments, the first calculating unit 31 includes:
the analyzing unit 311 is configured to obtain and analyze a first preset scene calculation function to obtain a function variable set, where the function variable set includes at least one parameter name.
The extracting unit 312 is configured to extract fourth information from the first information according to the parameter name, where the fourth information includes a value attribute corresponding to the parameter name.
The second calculating unit 313 is configured to calculate a first verification scene according to the first preset scene calculation function and the fourth information.
In some specific embodiments, the verification unit 32 includes:
the first logic unit 321 is configured to determine the annotation content of the field name, and if the field name is not annotated by the first preset annotation, determine the annotation content of the next field name.
The second logic unit 322 is configured to determine whether the value attribute corresponding to the field name is null if the field name is annotated by the first preset annotation, and determine the annotation content of the next field name if the value attribute corresponding to the field name is not null.
The third logic unit 323 is configured to determine whether the value attribute corresponding to the annotation of the first preset annotation is empty if the value attribute corresponding to the field name is empty, and mark the field name as a failed field name if the value attribute corresponding to the annotation of the first preset annotation is empty.
A fourth logic unit 324, configured to determine whether the value attribute corresponding to the first preset annotation includes the first check scenario if the value attribute corresponding to the first preset annotation is not null, and mark the field name as the failed field name if the value attribute corresponding to the first preset annotation includes the first check scenario.
In some specific embodiments, the verification unit 32 further includes:
a sixth logic unit 325, configured to send a first control command and retrieve the first information again if there is a failing field name, where the first control command includes a command for controlling the display to display that the failing field name cannot be empty.
It should be noted that, regarding the apparatus in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated herein.
Example 3:
corresponding to the above method embodiment, this embodiment further provides a data non-empty verification device, and a data non-empty verification device described below and a data non-empty verification method described above may be referred to in correspondence.
FIG. 3 is a block diagram illustrating a data non-null verification device 800 in accordance with an exemplary embodiment. As shown in fig. 3, the data non-null verification device 800 may include: a processor 801, a memory 802. The data non-null verification device 800 may also include one or more of a multimedia component 803, an I/O interface 804, and a communication component 805.
The processor 801 is configured to control the overall operation of the data non-null verification device 800, so as to complete all or part of the steps in the data non-null verification method. The memory 802 is used to store various types of data to support operation at the data non-empty verification device 800, such data may include, for example, instructions for any application or method operating on the data non-empty verification device 800, as well as application-related data, such as contact data, transceived messages, pictures, audio, video, and so forth. The Memory 802 may be implemented by any type of volatile or non-volatile Memory device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk or optical disk. The multimedia components 803 may include screen and audio components. Wherein the screen may be, for example, a touch screen and the audio component is used for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may further be stored in the memory 802 or transmitted through the communication component 805. The audio assembly also includes at least one speaker for outputting audio signals. The I/O interface 804 provides an interface between the processor 801 and other interface modules, such as a keyboard, mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 805 is used for wired or wireless communication between the data non-null verification device 800 and other devices. Wireless communication, such as Wi-Fi, bluetooth, Near Field Communication (NFC), 2G, 3G, or 4G, or a combination of one or more of them, so that the corresponding communication component 805 may include: Wi-Fi module, bluetooth module, NFC module.
In an exemplary embodiment, the data non-empty verification Device 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for performing the data non-empty verification method.
In another exemplary embodiment, a computer readable storage medium comprising program instructions which, when executed by a processor, implement the steps of the data non-null check method described above is also provided. For example, the computer readable storage medium may be the memory 802 described above that includes program instructions executable by the processor 801 of the data non-null verification device 800 to perform the data non-null verification method described above.
Example 4:
corresponding to the above method embodiment, this embodiment further provides a readable storage medium, and a readable storage medium described below and a data non-empty check method described above may be referred to correspondingly.
A readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the data non-null checking method of the above method embodiments.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and various other readable storage media capable of storing program codes.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes will occur to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (12)
1. A method of non-empty verification of data, comprising:
acquiring first information, wherein the first information comprises at least one filled parameter entity information, and the parameter entity information comprises at least one field name and a value attribute corresponding to the field name;
traversing all the annotations of the field names according to a first preset annotation to obtain the existence state of the first preset annotation, wherein the existence state comprises existence or nonexistence;
and when the existence state is existence, the existence state triggers and calls a non-empty check interceptor to carry out non-empty check on the first information.
2. The data non-empty-check method of claim 1, wherein the presence state triggering invoking a non-empty-check interceptor to perform non-empty check on the first information comprises:
calculating to obtain second information according to the first information, wherein the second information comprises a first check scene;
traversing the value attribute corresponding to each field name in the first information, and respectively performing non-empty check based on the second information to obtain third information, wherein the third information comprises a failed field name, and the failed field name is the field name for which the check fails.
3. The data non-empty checking method according to claim 2, wherein the calculating from the first information to obtain second information, the second information including a first checking scenario, includes:
acquiring and analyzing a first preset scene calculation function to obtain a function variable set, wherein the function variable set comprises at least one parameter name;
extracting fourth information from the first information according to the parameter name, wherein the fourth information comprises a value attribute corresponding to the parameter name;
and calculating to obtain a first verification scene according to the first preset scene calculation function and the fourth information.
4. The data non-empty checking method according to claim 2, wherein traversing the value attribute corresponding to each field name in the first information and performing non-empty checking based on the second information to obtain third information respectively comprises:
judging the annotation content of the field name, and if the field name is not annotated by the first preset annotation, judging the annotation content of the next field name;
if the field name is annotated by the first preset annotation, judging whether the value attribute corresponding to the field name is empty, and if not, judging the annotation content of the next field name;
if the value attribute corresponding to the field name is null, judging whether the value attribute corresponding to the annotation of the first preset annotation is null, and if the value attribute corresponding to the annotation of the first preset annotation is null, recording the field name as a failed field name;
if the value attribute corresponding to the first preset annotation note is not empty, judging whether the value attribute corresponding to the first preset annotation note contains a first verification scene, and if the value attribute corresponding to the first preset annotation note contains the first verification scene, recording the field name as a failed field name.
5. The data non-null checking method according to claim 4, wherein said recording said field name as a failed field name further comprises:
and if the failed field name exists, sending a first control command and re-acquiring the first information, wherein the first control command comprises a command for controlling a display to display that the failed field name cannot be null.
6. A data non-empty verification device, comprising:
the device comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring first information which comprises at least one filled parameter entity information, and the parameter entity information comprises at least one field name and a value attribute corresponding to the field name;
the first identification unit is used for traversing all the annotations of the field names according to a first preset annotation to obtain the existence state of the first preset annotation, and the existence state comprises existence or nonexistence;
and the trigger execution unit is used for triggering and calling a non-empty check interceptor to carry out non-empty check on the first information in the presence state.
7. The data non-empty checking device according to claim 6, wherein the trigger execution unit comprises:
the first calculation unit is used for calculating second information according to the first information, and the second information comprises a first check scene;
and the checking unit is used for traversing the value attribute corresponding to each field name in the first information and respectively performing non-empty checking on the basis of the second information to obtain third information, wherein the third information comprises a failed field name, and the failed field name is the field name which is failed in checking.
8. The data non-empty verification device of claim 7, wherein the first calculation unit comprises:
the analysis unit is used for acquiring and analyzing a first preset scene calculation function to obtain a function variable set, wherein the function variable set comprises at least one parameter name;
the extracting unit is used for extracting fourth information from the first information according to the parameter name, and the fourth information comprises a value attribute corresponding to the parameter name;
and the second calculating unit is used for calculating to obtain a first check scene according to the first preset scene calculating function and the fourth information.
9. The non-empty verification device of claim 7, wherein the verification unit comprises:
the first logic unit is used for judging the annotation content of the field name, and if the field name is not annotated by the first preset annotation, judging the annotation content of the next field name;
a second logic unit, configured to determine whether a value attribute corresponding to the field name is empty if the field name is annotated by the first preset annotation, and determine annotation content of a next field name if the value attribute corresponding to the field name is not empty;
a third logic unit, configured to determine whether the value attribute corresponding to the annotation of the first preset annotation is empty if the value attribute corresponding to the field name is empty, and mark the field name as a failed field name if the value attribute corresponding to the annotation of the first preset annotation is empty;
and the fourth logic unit is configured to determine whether the value attribute corresponding to the first preset annotation includes a first check scenario if the value attribute corresponding to the first preset annotation is not empty, and mark the field name as a failed field name if the value attribute corresponding to the first preset annotation includes the first check scenario.
10. The non-empty data verification device according to claim 9, wherein the verification unit further comprises:
and the sixth logic unit is used for sending a first control command and acquiring the first information again if the failing field name exists, wherein the first control command comprises a command for controlling the display to display that the failing field name cannot be null.
11. A data non-empty verification device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the data non-null checking method according to any one of claims 1 to 5 when executing said computer program.
12. A readable storage medium, characterized by: the readable storage medium has stored thereon a computer program which, when executed by a processor, carries out the steps of the data non-null verification method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210212907.9A CN114564206A (en) | 2022-03-04 | 2022-03-04 | Data non-empty checking method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210212907.9A CN114564206A (en) | 2022-03-04 | 2022-03-04 | Data non-empty checking method, device, equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114564206A true CN114564206A (en) | 2022-05-31 |
Family
ID=81718467
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210212907.9A Pending CN114564206A (en) | 2022-03-04 | 2022-03-04 | Data non-empty checking method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114564206A (en) |
-
2022
- 2022-03-04 CN CN202210212907.9A patent/CN114564206A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109344642B (en) | Interface rule checking method, device, computer equipment and storage medium | |
| US10554805B2 (en) | Information processing method, terminal, and computer-readable storage medium | |
| WO2019169723A1 (en) | Test case selection method, device and equipment, and computer-readable storage medium | |
| CN110209684A (en) | Tracking, device, system and the medium of database D DL change operation | |
| CN111552633A (en) | Interface abnormal call testing method and device, computer equipment and storage medium | |
| CN110795175A (en) | Method and device for analog control of intelligent terminal and intelligent terminal | |
| CN114238948A (en) | Application program detection method and device, electronic equipment and storage medium | |
| CN111400170A (en) | Data permission testing method and device | |
| CN106358220B (en) | The detection method of abnormal contact information, apparatus and system | |
| CN109634838A (en) | Position method, apparatus, storage medium and the electronic equipment of application failure | |
| CN111124627B (en) | Method and device for determining call initiator of application program, terminal and storage medium | |
| CN109376085B (en) | Test case generation method and device and computer readable storage medium | |
| CN110362294A (en) | Development task executes method, apparatus, electronic equipment and storage medium | |
| CN112817782B (en) | Data acquisition reporting method and device, electronic equipment and storage medium | |
| CN114564206A (en) | Data non-empty checking method, device, equipment and readable storage medium | |
| CN112988304B (en) | Recording method and device of operation mode, electronic equipment and storage medium | |
| CN111880996B (en) | Bare metal data acquisition method, device, equipment and readable storage medium | |
| CN114968960A (en) | Log processing method and device, computer equipment and storage medium | |
| CN114579136A (en) | Code processing method and device, computer equipment and storage medium | |
| CN114372043A (en) | Data migration method and device, electronic equipment and storage medium | |
| CN114428737A (en) | Communication method, device, equipment and storage medium based on micro service system | |
| CN113076728A (en) | Data filling method of dialog box and related equipment | |
| CN112948264A (en) | Test task execution method, device, system, storage medium and electronic device | |
| CN112306723A (en) | Operation information acquisition method and device applied to small program | |
| CN108681594A (en) | Document handling method and relevant apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |