CN106991023B - Interface parameter checking method and component - Google Patents
Interface parameter checking method and component Download PDFInfo
- Publication number
- CN106991023B CN106991023B CN201710171782.9A CN201710171782A CN106991023B CN 106991023 B CN106991023 B CN 106991023B CN 201710171782 A CN201710171782 A CN 201710171782A CN 106991023 B CN106991023 B CN 106991023B
- Authority
- CN
- China
- Prior art keywords
- rule
- interface
- parameter
- verification
- module
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
- G06F11/221—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested to test buses, lines or interfaces, e.g. stuck-at or open line faults
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
- G06F11/2215—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested to test error correction or detection circuits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
Abstract
The invention provides an interface parameter checking method, which comprises the following steps: the client self-defines the parameters through the client, the annotation analysis module analyzes the parameters and sends analysis result data to the verification rule generation module, the check rule generating module generates a comparison rule of the custom reference data type according to the analysis result data, the annotation checking module searches the corresponding attribute in the parameter object according to the attributes of the comparison rule generated by the checking rule generating module one by one, then the values of the attributes are compared through a self-defined comparison rule, if the corresponding attribute is not found or the attribute values corresponding to the attribute are different, the verification fails, otherwise, the verification passes, the interface parameter checking method can realize the diversification of the frame based on various formats of annotation, json and xml, better supports the strong dependence of parameters and can support complex parameter types.
Description
Technical Field
The invention relates to the technical field of interface inspection, in particular to an interface parameter checking method and an interface parameter checking assembly.
Background
It is known that there will be parameters as long as there is an interface, but there is a check of the parameters. For the service interface, the service code should be clear at a glance, and only the logic idea related to the service exists, but there should not be a large number of if-ifs for checking the parameters or the data itself or some other processing, and the checking processing of the interface parameters is very important in order to enhance the readability and maintainability of the code.
Many popular open source frameworks today have their own parameter checking mechanisms, such as struts2, Validator mechanism by spring mvc, hibernate-Validator, common-Validator, etc.;
for many scenarios, these third-party components cannot meet our needs, such as parameter dependencies and the like. They are simply the format that provides the check parameter field and these checkers 2020 are stateful, resulting in poor performance of the check. It is very laborious to handle some operations with large data volumes. For the pursuit of high performance of internet platforms, inefficient interfaces are often not available.
Therefore, a need exists in the art for a method and an assembly for checking interface parameters, which can implement diversification of a frame based on multiple formats of annotation, json and xml, better support strong dependency of parameters, support complex parameter types, unify interface development mode standards, standardize code consistency, enhance system stability, easy maintenance and robustness, enhance code readability and maintainability, and more accurately check interface parameters.
Disclosure of Invention
The technical problem to be solved by the invention is to provide an interface parameter checking method and an interface parameter checking assembly, the interface parameter checking method can be used for realizing the diversification of a frame based on various formats such as annotation, json and xml, better supports the strong dependence of parameters, can support complex parameter types, unifies the interface development mode standard, standardizes the code consistency, enhances the stability, the easy maintenance and the robustness of a system, enhances the readability and the maintainability of codes, and more accurately checks interface parameters.
In order to solve the technical problem, the invention provides an interface parameter checking method, which comprises a client, a checker and a server, wherein the checker comprises an annotation analysis module, an annotation checking module and a checking rule generation module, and the interface parameter checking method comprises the following steps: the client requests an interface of the server, the client self-defines parameters through the client, the annotation analysis module analyzes the parameters and sends analysis result data to the verification rule generation module, the verification rule generation module generates a comparison rule of self-defining reference data types according to the analysis result data, the annotation verification module searches for attributes corresponding to the parameter objects according to attributes of the comparison rule generated by the verification rule generation module one by one, and then compares values of the attributes through the self-defined comparison rule, if the corresponding attributes are not found or the attribute values corresponding to the attributes are different, verification fails, otherwise, verification passes.
Preferably, the annotation checking module supports xml configuration, json configuration, and java based custom annotation configuration.
Preferably, the step of generating a comparison rule of a custom reference data type according to the parsing result data by the verification rule generating module includes:
the verification rule generating module generates a basic type self-defining rule according to the analysis result data;
the check rule generating module generates a user-defined check rule according to the analysis result data;
the implementation basic type self-defining rules comprise must, int, strin, len, date, reg, long, float and double.
Preferably, the rule must is implemented as: the rule specifies that the field is necessary and cannot be null or an empty string;
the realization of the rule int is that the field specified by the rule is not null or empty string, and is int type data, and the field must be within the specified size;
the implementation of the rule strin is that if the field specified by the rule is not null or empty, the field is required to be one of the specified string arrays;
the rule len is realized in such a way that a field specified by the rule is not null or an empty string and is required to be specified in length;
the implementation of the rule date is that the field specified by the rule is not null or empty string and is required to be in a specified date format;
the realization of the rule reg is that the field specified by the rule is not null or empty string and is required to be matched with a specified regular expression;
the implementation of the rule long is that the field specified by the rule is not null or empty string, and is long type data and must be within the specified size;
the rule float is implemented in such a way that the fields specified by the rule, which are not null or empty strings, are float-type data and must be within a specified size.
The rule double is implemented in such a way that the field specified by the rule, which is not null or empty, is data of double type and must be within a specified size.
Preferably, the step of generating the customized verification rule according to the analysis result data by the verification rule generation module includes:
the verification rule generating module defines the logic of a rule object and a parameter object of a validateRuleHandler interface;
and adding a custom rule according to the rule object and the parameter object, and configuring a complete path of the processor of the custom rule.
Preferably, the rule Object of the validateRuleHandler interface is a RuleInfo Object, the RuleInfo Object is a rule Object generated by interface parameters defined by implementation of a service interface to be checked, the parameter Object is a filevalue-Object, and the filevalue-Object is a parameter Object generated by parameters transmitted by a service interface caller.
Preferably, the step of implementing, by the annotation verification module, the step of finding the attribute corresponding to the comparison rule in the parameter object according to the attribute-by-attribute of the comparison rule generated by the verification rule generation module, and then comparing the values of the attributes by the customized comparison rule includes:
the annotation checking module acquires parameters transmitted by the client and packages the parameters into parameter objects, acquires corresponding rule objects according to the parameter objects annotated by the annotation analyzing module, searches attributes corresponding to the rule objects, compares values of the attributes through a customized comparison rule, if the checking is successful, the service logic of the interface is executed, otherwise, the service logic of the interface is not executed.
Preferably, the interface parameter checking method further includes: and the annotation checking module returns the checking result to the parameter object of the client.
Preferably, the check rule generation module further generates a rule for field global necessity check.
In order to solve the technical problem, the invention also provides an interface parameter checking component of the interface parameter checking method;
after the method and the components are adopted, the client requests an interface of the server, the checker comprises an annotation analysis module, an annotation check module and a check rule generation module, the client self-defines parameters through the client, the annotation analysis module analyzes the parameters and sends analysis result data to the check rule generation module, the check rule generation module generates a comparison rule of self-defining reference data types according to the analysis result data, the annotation check module searches attributes corresponding to the parameter objects according to the attributes of the comparison rule generated by the check rule generation module one by one, then compares the values of the attributes through the self-defining comparison rule, if the corresponding attributes are not found or the attribute values corresponding to the attributes are different, the check is failed, otherwise, the interface parameter verification method can realize the diversification of the frame based on various formats such as annotation, json and xml, better support the strong dependence of parameters, support the complex parameter types, unify the interface development mode standard, standardize the code consistency, enhance the stability, the maintainability and the robustness of the system, enhance the readability and the maintainability of the code and more accurately verify the interface parameters.
Drawings
FIG. 1 is a flow chart illustrating the implementation of a method for checking interface parameters according to the present invention;
fig. 2 is a schematic diagram of an overall model of an interface parameter verification method according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Example 1
Referring to fig. 1 to 2 of the drawings,
FIG. 1 is a flow chart illustrating the implementation of a method for checking interface parameters according to the present invention;
fig. 2 is a schematic diagram of an overall model of an interface parameter verification method according to the present invention.
The invention discloses an interface parameter checking method, which provides a client 10, a checker 20 and a server 30, wherein the checker 20 comprises an annotation analysis module 21, an annotation checking module 22 and a checking rule generation module 23, and the interface parameter checking method comprises the following steps: the client 10 requests an interface of the server, the client customizes parameters through the client 10, the annotation parsing module 21 parses the parameters and sends the parsing result data to the verification rule generating module 23, the check rule generating module 23 generates a comparison rule of the custom reference data type according to the parsing result data, the annotation checking module 22 finds the corresponding attribute in the parameter object according to the attributes of the comparison rule generated by the checking rule generating module 23, then the values of the attributes are compared through a self-defined comparison rule, if the corresponding attribute is not found or the corresponding attribute values are different, the verification fails, otherwise, the annotation verification module 22 returns the verification result to the parameter object of the client 10.
In this embodiment, the preferred annotation checking module 22 supports xml configuration, json configuration, and java-based customized annotation configuration, and can better perform unified management on the parameters of the interface, so that the service logic of the interface is more flexible.
In this embodiment, the interface parameter verification method adds a technical solution implemented based on xml configuration and json configuration: xml and json are main communication tool languages for performing front-end and back-end interaction, communication between interfaces and even cross-service and cross-system at present, and compared with an annotation implementation mode, xml and json formats have clearer parameter rule structures and relatively more excellent readability of codes, but the xml and json formats have the defects of being not concise and relatively complicated to use in a development process. But the same principles as in the previous figure are applied to the idea of the underlying implementation. The method is characterized in that only the analyzed objects are different, the xml or json object is used for analyzing the itemized attribute values of xmldocument and json object into corresponding javabeans through xmlPaser and json Paser, and then check matching is carried out, so that the availability and diversity of the framework are enhanced.
In this embodiment, the step of generating the comparison rule of the self-defined reference data type according to the parsing result data by the verification rule generating module 23 includes:
the check rule generating module 23 generates a basic type self-defining rule according to the analysis result data;
the check rule generating module 23 generates a custom check rule according to the analysis result data;
the implementation basic type self-defining rules comprise must, int, strin, len, date, reg, long, float and double.
In this embodiment, the rule must is implemented as follows: the rule specifies that the field is necessary and cannot be null or an empty string;
the realization of the rule int is that the field specified by the rule is not null or empty string, and is int type data, and the field must be within the specified size;
the implementation of the rule strin is that if the field specified by the rule is not null or empty, the field is required to be one of the specified string arrays;
the rule len is realized in such a way that a field specified by the rule is not null or an empty string and is required to be specified in length;
the implementation of the rule date is that the field specified by the rule is not null or empty string and is required to be in a specified date format;
the realization of the rule reg is that the field specified by the rule is not null or empty string and is required to be matched with a specified regular expression;
the implementation of the rule long is that the field specified by the rule is not null or empty string, and is long type data and must be within the specified size;
the rule float is implemented in such a way that the fields specified by the rule, which are not null or empty strings, are float-type data and must be within a specified size.
The rule double is implemented in such a way that the field specified by the rule, which is not null or empty, is data of double type and must be within a specified size.
In this embodiment, the step of generating the customized verification rule according to the analysis result data by the verification rule generating module 23 includes:
the check rule generating module 23 defines the logic of the rule object and the parameter object of the validateRuleHandler interface;
and adding a custom rule according to the rule object and the parameter object, and configuring a complete path of the processor of the custom rule.
The rule Object of the validateRuleHandler interface is a RuleInfo Object, the RuleInfo Object is a rule Object generated by interface parameters which are well defined by the realization of a service interface needing to be checked, the parameter Object is a fileValue-Object Object, and the fileValue-Object Object is a parameter Object generated by parameters transmitted by a service interface calling party.
The step of implementing, by the annotation check module 22, the step of finding the attribute corresponding to the comparison rule in the parameter object according to the attribute-by-attribute of the comparison rule generated by the check rule generation module 23, and then comparing the values of the attributes by the customized comparison rule includes:
the annotation checking module 22 obtains the parameters transmitted from the client 10 and packages them into parameter objects, obtains the corresponding rule objects according to the parameter objects annotated by the annotation parsing module 21, searches for the attributes corresponding to the rule objects, compares the values of the attributes by a customized comparison rule, if the checking is successful, the service logic of the interface is executed, otherwise, the service logic of the interface is not executed.
In this embodiment, the check rule generating module 23 further generates a rule for checking field global necessity, and the check of field necessity is implemented by a must check rule, but if it is desired to require necessity check for all fields, a new field global necessity setting is added, a must indicates that all fields cannot be null, a ge is defined as an int integer greater than 1, and a single exclamation point "|! "presentation may be empty (higher priority than best). Of course, best defaults to false when not configured, and all fields do not require a necessity check. If a field requires a necessity check, two exclamation marks "! | A ", for example:
@ Validate (value: "age: int (1, M) | status: string (0,1,2) | name: len (4)") indicates that no other fields are required except that age requires a necessity check.
The invention also discloses an interface parameter checking component for realizing the interface parameter checking method, which comprises a client 10, a checker 2020 and a server 30, wherein the checker 2020 comprises an annotation parsing module 21, an annotation checking module 22 and a checking rule generating module 23, the client 10 requests an interface of a server, a client self-defines parameters through the client 10, the annotation parsing module 21 parses the parameters and sends parsing result data to the checking rule generating module 23, the checking rule generating module 23 generates a comparison rule of self-defining reference data types according to the parsing result data, the annotation checking module 22 searches corresponding attributes in parameter objects according to the one-by-one attributes of the comparison rule generated by the checking rule generating module 23, and then compares the values of the attributes through the self-defining comparison rule, if the corresponding attribute is not found or the attribute values corresponding to the attribute are different, the verification is failed, otherwise, the verification is passed.
After the method and the components are adopted, the client 10 requests an interface of the server, the verifier 2020 includes an annotation parsing module 21, an annotation checking module 22 and a checking rule generating module 23, the client self-defines parameters through the client 10, the annotation parsing module 21 parses the parameters and sends parsing result data to the checking rule generating module 23, the checking rule generating module 23 generates a comparison rule of self-defined reference data types according to the parsing result data, the annotation checking module 22 searches attributes corresponding to the parameters in the parameter object according to the attributes of the comparison rule generated by the checking rule generating module 23 one by one, then compares the values of the attributes through the self-defined comparison rule, if the corresponding attributes are not found or the attribute values corresponding to the attributes are not the same, if the verification fails, otherwise, the verification passes, the interface parameter verification method can realize the diversification of the frame based on multiple formats of annotation, json and xml, better support the strong dependence of the parameters, support the complex parameter types, unify the interface development mode standard, standardize the code consistency, enhance the stability, the maintainability and the robustness of the system, enhance the readability and the maintainability of the codes and more accurately perform the verification processing on the interface parameters.
Meanwhile, it should be understood that the above is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent structures or equivalent implementation methods using the contents of the present specification and the drawings, or other related technical fields, are included in the scope of the present invention.
Claims (5)
1. An interface parameter checking method is characterized in that: providing a client, a verifier and a server, wherein the verifier comprises an annotation analysis module, an annotation verification module and a verification rule generation module, and the interface parameter verification method comprises the following steps: the client requests an interface of the server, the client self-defines parameters through the client, the annotation analysis module analyzes the parameters and sends analysis result data to the verification rule generation module, the verification rule generation module generates a comparison rule of self-defined reference data types according to the analysis result data, the annotation verification module searches attributes corresponding to the parameter objects according to attributes of the comparison rule generated by the verification rule generation module one by one, and then compares values of the attributes through the self-defined comparison rule, if the corresponding attributes are not found or the attribute values corresponding to the attributes are different, the verification fails, otherwise, the verification passes;
the annotation checking module supports xml configuration, json configuration and java-based self-defined annotation configuration, analyzes the attribute values of an xml file or a json object one by one to form corresponding java beans through xmlPaser and json Paser, and then checks and matches;
the step of generating the comparison rule of the user-defined reference data type by the verification rule generating module according to the analysis result data comprises the following implementation steps:
the verification rule generating module generates a basic type self-defining rule according to the analysis result data;
the check rule generating module generates a user-defined check rule according to the analysis result data;
the implementation basic type self-defining rules comprise a rule must, a rule int, a rule strin, a rule len, a rule date, a rule reg, a rule long, a rule float and a rule double;
the implementation of the rule must is: the rule specifies that the field is necessary and cannot be null or an empty string;
the realization of the rule int is that the field specified by the rule is not null or empty string, and is int type data, and the field must be within the specified size;
the implementation of the rule strin is that if the field specified by the rule is not null or empty, the field is required to be one of the specified string arrays;
the rule len is realized in such a way that a field specified by the rule is not null or an empty string and is required to be specified in length;
the implementation of the rule date is that the field specified by the rule is not null or empty string and is required to be in a specified date format;
the realization of the rule reg is that the field specified by the rule is not null or empty string and is required to be matched with a specified regular expression;
the implementation of the rule long is that the field specified by the rule is not null or empty string, and is long type data and must be within the specified size;
the rule float is realized in such a way that a field specified by the rule is not null or empty string, is float-type data and must be within a specified size;
the rule double is realized in such a way that a field specified by the rule is not null or empty string, is double-type data and must be within a specified size;
the step of generating the user-defined check rule by the check rule generating module according to the analysis result data comprises the following steps:
the verification rule generating module defines the logic of a rule object and a parameter object of a validateRuleHandler interface;
adding a self-defining rule according to the rule object and the parameter object, and configuring a complete path of a processor of the self-defining rule;
the rule Object of the validateRuleHandler interface is a RuleInfo Object, the RuleInfo Object is a rule Object generated by interface parameters which are well defined by the realization of a service interface needing to be checked, the parameter Object is a fileValue-Object Object, and the fileValue-Object Object is a parameter Object generated by parameters transmitted by a service interface calling party.
2. The interface parameter verification method of claim 1, wherein: the step of implementing that the annotation check module searches the corresponding attribute in the parameter object according to the attributes of the comparison rule generated by the check rule generation module one by one, and then compares the values of the attributes through the customized comparison rule includes the following steps:
the annotation checking module acquires parameters transmitted by the client and packages the parameters into parameter objects, acquires corresponding rule objects according to the parameter objects annotated by the annotation analyzing module, searches attributes corresponding to the rule objects, compares values of the attributes through a customized comparison rule, if the checking is successful, the service logic of the interface is executed, otherwise, the service logic of the interface is not executed.
3. The interface parameter verification method of claim 2, wherein: the interface parameter checking method further comprises the following steps: and the annotation checking module returns the checking result to the parameter object of the client.
4. The interface parameter verification method of claim 2, wherein: the check rule generation module also generates a rule for field global necessity checking.
5. An interface parameter verification system, comprising: the method comprises a client, a checker and a server, wherein the client, the checker and the server are used for realizing the interface parameter checking method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710171782.9A CN106991023B (en) | 2017-03-22 | 2017-03-22 | Interface parameter checking method and component |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710171782.9A CN106991023B (en) | 2017-03-22 | 2017-03-22 | Interface parameter checking method and component |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106991023A CN106991023A (en) | 2017-07-28 |
| CN106991023B true CN106991023B (en) | 2020-10-09 |
Family
ID=59412160
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710171782.9A Active CN106991023B (en) | 2017-03-22 | 2017-03-22 | Interface parameter checking method and component |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106991023B (en) |
Families Citing this family (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109656744A (en) * | 2017-10-11 | 2019-04-19 | 北京京东尚科信息技术有限公司 | The method and apparatus for realizing data check and injection are explained based on Java |
| CN108132880B (en) * | 2017-12-21 | 2020-07-07 | 武汉斑马快跑科技有限公司 | Parameter checking method and device |
| CN108388430A (en) * | 2018-01-26 | 2018-08-10 | 珠海金山网络游戏科技有限公司 | A kind of mobile terminal data check system and method |
| CN108415834A (en) * | 2018-02-12 | 2018-08-17 | 平安科技（深圳）有限公司 | Explain rear end method of calibration, device, computer equipment and storage medium |
| CN110554929B (en) * | 2018-06-04 | 2023-07-07 | 百度在线网络技术（北京）有限公司 | Data verification method, device, computer equipment and storage medium |
| CN109194643B (en) * | 2018-08-29 | 2021-02-26 | 创新先进技术有限公司 | Data transmission and message analysis method, device and equipment |
| CN110968888B (en) * | 2018-09-30 | 2022-03-08 | 北京国双科技有限公司 | Data processing method and device |
| CN111046067A (en) * | 2018-10-11 | 2020-04-21 | 北京京东尚科信息技术有限公司 | Data judgment method and device |
| CN109739573B (en) * | 2018-12-27 | 2023-07-18 | 深圳市多度科技有限公司 | Processing method and device for realizing API (application program interface) call and system for realizing API |
| CN110489265A (en) * | 2019-03-07 | 2019-11-22 | 西安博达软件股份有限公司 | A kind of JSON data validation and storage method based on metadata |
| CN110147261A (en) * | 2019-04-15 | 2019-08-20 | 平安普惠企业管理有限公司 | Parameter verification method and relevant device based on calling interface |
| CN110347999A (en) * | 2019-07-17 | 2019-10-18 | 政采云有限公司 | A kind of method and apparatus of list data verification |
| CN112650488A (en) * | 2019-10-12 | 2021-04-13 | 上海际链网络科技有限公司 | Parameter checking method and device, storage medium and service terminal |
| CN111191246A (en) * | 2019-12-19 | 2020-05-22 | 杭州安恒信息技术股份有限公司 | Spring annotation based security development verification method |
| CN111078570B (en) * | 2019-12-20 | 2023-04-07 | 贵阳货车帮科技有限公司 | Parameter format detection method, device, equipment and medium based on interface framework |
| CN111897842A (en) * | 2020-01-02 | 2020-11-06 | 北京京东尚科信息技术有限公司 | Data checking method, device, computer system and medium |
| CN111158792B (en) * | 2020-01-02 | 2023-05-16 | 普元信息技术股份有限公司 | Service parameter verification processing system and method capable of realizing dynamic configuration under distributed architecture |
| CN112181804B (en) * | 2020-08-31 | 2023-09-08 | 五八到家有限公司 | Parameter verification method, device and storage medium |
| CN112182037B (en) * | 2020-09-28 | 2024-03-29 | 百度在线网络技术（北京）有限公司 | Data verification method, device, equipment and storage medium |
| CN112241370B (en) * | 2020-10-21 | 2023-06-16 | 网易（杭州）网络有限公司 | API interface class checking method, system and device |
| CN112631695A (en) * | 2020-12-22 | 2021-04-09 | 北京达佳互联信息技术有限公司 | Data verification method and device, electronic equipment and storage medium |
| CN112612720A (en) * | 2020-12-31 | 2021-04-06 | 中国农业银行股份有限公司 | Attribute checking method, attribute checking device, attribute checking equipment and attribute checking medium |
| CN113190539A (en) * | 2021-04-20 | 2021-07-30 | 鼎蓝惠民信息技术(西安)有限公司 | Method for standardized verification of affair elements based on national government affair service |
| CN117707653A (en) * | 2024-02-06 | 2024-03-15 | 天津医康互联科技有限公司 | Parameter monitoring method, device, electronic equipment and computer readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2587401A1 (en) * | 2011-10-27 | 2013-05-01 | Sap Ag | Enforcing input validation through aspect oriented programming |
| CN105677326A (en) * | 2015-12-28 | 2016-06-15 | 国云科技股份有限公司 | Software interface parameter validation method |
-
2017
- 2017-03-22 CN CN201710171782.9A patent/CN106991023B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2587401A1 (en) * | 2011-10-27 | 2013-05-01 | Sap Ag | Enforcing input validation through aspect oriented programming |
| CN105677326A (en) * | 2015-12-28 | 2016-06-15 | 国云科技股份有限公司 | Software interface parameter validation method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106991023A (en) | 2017-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106991023B (en) | Interface parameter checking method and component | |
| US10108535B2 (en) | Web application test script generation to test software functionality | |
| US9110945B2 (en) | Support for a parameterized query/view in complex event processing | |
| KR102214297B1 (en) | Conditional validation rules | |
| KR101755365B1 (en) | Managing record format information | |
| US10572370B2 (en) | Test-assisted application programming interface (API) learning | |
| US9588742B2 (en) | Rule-based automatic class generation from a JSON message | |
| AU2014287654B2 (en) | Parser generation | |
| US20160350303A1 (en) | Management Of Structured, Non-Structured, And Semi-Structured Data In A Multi-Tenant Environment | |
| US20170364386A1 (en) | Event-Driven Multi-Tenant Computer-Management Platform | |
| CN108984567A (en) | A kind of Service Data Management system and method | |
| CN111581920A (en) | Document conversion method, device, equipment and computer storage medium | |
| CN108762743A (en) | Data table operation code generation method and device | |
| CN110427188A (en) | It is single to survey configuration method, device, equipment and the storage medium for asserting program | |
| US10382353B1 (en) | Enhancing incomplete cloud templates for infrastructure deployment | |
| CN113127108A (en) | Service request processing method and device, storage medium and electronic equipment | |
| CN111814449A (en) | Form analysis method, device, equipment and storage medium | |
| CN113760987A (en) | Data processing method and data processing platform | |
| CN108829968A (en) | Circuit diagram checking method based on Python spread function | |
| US20090007083A1 (en) | Techniques for parsing electronic files | |
| CN108959508A (en) | SQL data creation method and device | |
| CN114185797A (en) | Front-end code checking method and device, electronic equipment and readable storage medium | |
| CN117632710A (en) | Method, device, equipment and storage medium for generating test code | |
| CN115268924A (en) | Formula calculation engine service method and system based on aPaaS platform | |
| CN114564182A (en) | Command line checking method and device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 518000 R & D room 3501, block a, building 7, Vanke Cloud City Phase I, Xingke 1st Street, Xili community, Xili street, Nanshan District, Shenzhen City, Guangdong Province Patentee after: Tubatu Group Co.,Ltd. Address before: 1001-a, 10th floor, bike technology building, No.9, Keke Road, high tech Zone, Nanshan District, Shenzhen, Guangdong 518000 Patentee before: SHENZHEN BINCENT TECHNOLOGY Co.,Ltd. |