CN116303056A - A component library verification method, system, device and storage medium - Google Patents

Abstract

An embodiment of the present invention provides a component library verification method, system, device, and storage medium method, wherein the method includes: obtaining the storage address of the target component library input by the user, and performing information verification on the target component library based on the storage address , when the content of the verification result of the information verification is verification passed, obtain the component library verification command input by the user, identify the verification type of the component library verification command, and call the preset verification command group corresponding to the verification type, and verify the target The component library performs verification and outputs the verification result. The invention improves the verification efficiency of the component library.

Description

A component library verification method, system, device and storage medium

technical field

The invention relates to the field of computer technology, in particular to a component library verification method, system, equipment and storage medium.

Background technique

In the process of developing software based on the iOS platform, along with the increase in the complexity of software functions, the types and quantities of source codes of open source projects to be referenced are also increasing. This makes it necessary to use many built-in commands of the dependency manager in the process of verifying and publishing the built component library.

However, due to the increase in the types and quantities of source codes of open source projects cited, the number of built-in commands to be called during verification also increases, which makes developers need to call built-in commands when verifying and publishing component libraries. also increased. And because developers have different mastery of the built-in commands of the dependent library, it is prone to risks such as missing or wrongly calling commands due to the increase in the number of commands that need to be called, which reduces the verification efficiency of the component library. At the same time, in order to solve the above problems, some developers use their own development and verification and issue commands instead of built-in commands to perform corresponding operations. However, since the accuracy of self-developed commands depends on the developer's development level, the reliability of complex component library verification based on self-developed commands is low, and the verification efficiency of component libraries cannot be improved.

Contents of the invention

The purpose of the embodiment of the present invention is to provide a component library verification method, system, device and storage medium, so as to realize the purpose of the invention of improving the verification efficiency of the component library. The specific technical scheme is as follows:

A component library verification method, the method comprising:

Obtaining the storage address of the target component library input by the user, and performing information verification on the target component library based on the storage address;

If the content of the verification result of the information verification is that the verification is passed, obtain a component library verification instruction input by the user;

Identifying the verification type of the component library verification instruction, calling a preset verification instruction group corresponding to the verification type, verifying the target component library, and outputting a verification result.

Optionally, identifying the verification type of the verification instruction of the component library, and calling a preset verification instruction group corresponding to the verification type to verify the target component library, and output the verification result, including :

Using a preset character string matching algorithm to identify the component library verification instruction to obtain the verification type;

Determining a verification instruction group identifier corresponding to the verification type;

Invoke the preset verification instruction group with the verification instruction group identifier, verify the target component library, and output the verification result.

Optionally, the obtaining the storage address of the target component library input by the user, and performing information verification on the target component library based on the storage address includes:

Obtaining the storage address of the target component library input by the user, accessing the storage address, and judging whether file data whose data type is an index file is stored in the storage address;

In the case where the file data is stored in the storage address, determine whether the target component library is stored in the storage address, if so, read the version number of the target component library in the file data and configuration information, judging whether the version number is consistent with the version label of the target component library, and judging whether the source code information in the target component library is consistent with the configuration information;

When the version number is consistent with the version label, and the source code information is consistent with the configuration information, the output content is a verification result of the information verification that passes the verification.

Optionally, in the case that the verification instruction identifier includes an identifier for local verification, the call is made to a preset verification instruction group with the verification instruction group identifier, the target component library is verified, and the verification result is output ,include:

Invoking the preset verification instruction group with the verification instruction group identifier representing the identifier for the local verification, reading the dependent library information of the target component library, and obtaining the storage address of the dependent source code;

Obtaining the dependent source code stored in the storage address of the dependent source code, and locally compiling the dependent source code;

If the local compilation of the dependent source code is successful, it is determined that the local verification of the target component library is passed, and the verification result that the verification is passed is output.

Optionally, in the case where the verification instruction identifier includes an identifier representing remote verification, the calling of a preset verification instruction group with the verification instruction group identifier verifies the target component library, and outputs Verify results, including:

Invoking the preset verification instruction group with the verification instruction group identifier representing the identifier for the remote verification, obtaining the index file stored in the storage address, and remotely storing the address according to the source code in the index file, Obtaining source code data of the target component library;

Perform local compilation on the source code data, and if the local compilation is successful, determine that the remote verification of the target component library has passed, and output the verification result whose content is that the verification has passed.

Optionally, in the case where the verification instruction identifier includes an identifier for version verification, the call is made to a preset verification instruction group with the verification instruction group identifier, the target component library is verified, and the verification result is output ,include:

Invoke the preset verification instruction group with the identification of the verification instruction group for the version verification, obtain the index file stored in the storage address, and obtain the target version according to the remote storage address of the version in the index file component library;

The local compilation is performed on the target version component library, and if the local compilation is successful, it is determined that the version verification of the target component library is passed, and the verification result is output as the verification result.

Optionally, the method also includes:

When the content of the verification result is that the verification is passed, and the component library release command is received, the component library release command is invoked, and the index file of the target component library is sent to the address corresponding to the target remote file index warehouse address input by the user. storage in the storage area to complete the release of the target component library.

A component library verification system, the system comprising:

An information verification module, configured to obtain the storage address of the target component library input by the user, and perform information verification on the target component library based on the storage address;

An instruction obtaining module, configured to obtain the component library verification instruction input by the user when the content of the verification result of the information verification is verified;

The verification module is used to identify the verification type of the verification instruction of the component library, and construct, deploy, and issue a preset verification instruction group corresponding to the verification type to verify the target component library, and input the method The verification result is displayed.

Optionally, the verification module is set to:

Using a preset character string matching algorithm to identify the component library verification instruction to obtain the verification type;

Determining a verification instruction group identifier corresponding to the verification type;

Invoke the preset verification instruction group with the verification instruction group identifier, verify the target component library, and output the verification result.

Optionally, the information verification module is set to:

Obtaining the storage address of the target component library input by the user, accessing the storage address, and judging whether file data whose data type is an index file is stored in the storage address;

In the case where the file data is stored in the storage address, determine whether the target component library is stored in the storage address, if so, read the version number of the target component library in the file data and configuration information, judging whether the version number is consistent with the version label of the target component library, and judging whether the source code information in the target component library is consistent with the configuration information;

When the version number is consistent with the version label, and the source code information is consistent with the configuration information, the output content is a verification result of the information verification that passes the verification.

Optionally, the verification module is specifically set as:

In the case that the verification instruction identifier includes an identifier for local verification, call the preset verification instruction group with the verification instruction group identifier for the local verification identifier, and read the dependency of the target component library Library information to obtain the storage address of the dependent source code;

Obtaining the dependent source code stored in the storage address of the dependent source code, and locally compiling the dependent source code;

If the local compilation of the dependent source code is successful, it is determined that the local verification of the target component library is passed, and the verification result that the verification is passed is output.

Optionally, the verification module is specifically set as:

In the case that the verification instruction identifier includes an identifier for performing remote verification, the method calls to construct a preset verification instruction group with the identification of the verification instruction group issuing the identifier for performing remote verification. Obtain the index file stored in the storage address, and obtain the source code data of the target component library according to the source code remote storage address in the index file;

Perform local compilation on the source code data, and if the local compilation is successful, determine that the remote verification of the target component library has passed, and output the verification result whose content is that the verification has passed.

Optionally, the verification module is specifically set as:

In the case that the verification instruction identifier includes an identifier representing version verification, calling a preset verification instruction group with the verification instruction group identifier representing the version verification, and obtaining the index stored in the storage address file, and obtain the target version component library according to the version remote storage address in the index file;

The local compilation is performed on the target version component library, and if the local compilation is successful, it is determined that the version verification of the target component library is passed, and the verification result is output as the verification result.

Optionally, the component library verification system also includes:

The publishing module is used to call the component library to issue the command when the content of the verification result is that the verification is passed and the command to issue the component library is received, and send the index file of the target component library to the target remote file input by the user The storage area corresponding to the index warehouse address is stored, and the release of the target component library is completed.

A component library verification device, the device comprising:

processor;

memory for storing said processor-executable instructions;

Wherein, the processor is configured to execute instructions to implement the component library verification method described in any one of the above.

A computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by the processor of the component library verification device, the component library verification device can perform the component library verification as described in any one of the above method.

The embodiment of the present invention provides a component library verification method, system, device, and storage medium construction, and can be released to verify the information of the target component library based on the storage address input by the user, which can avoid the method due to the storage address The version or configuration of the stored component library is inconsistent with the version or configuration of the target component library to be released, which will cause the component library verification to fail, thereby reducing the risk of verification efficiency. Moreover, by establishing a preset instruction group that can be automatically run, and establishing the corresponding relationship between the verification type of the component library verification instruction and the preset verification instruction group, users do not need to learn and understand the huge built-in instructions of the source code management tool. Inputting the component library verification instruction corresponding to the verification steps to be performed can automatically realize the comprehensive verification of the target component library. Improved verification efficiency for component libraries. It can be seen that the present invention improves the verification efficiency of the component library.

Of course, implementing any product or method of the present invention does not necessarily need to achieve all the above-mentioned advantages at the same time.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

Fig. 1 is a flow chart of a component library verification method provided by an embodiment of the present invention;

FIG. 2 is a schematic diagram of an instruction input interface provided by an optional embodiment of the present invention;

Fig. 3 is a flow chart of a component library verification method provided by another optional embodiment of the present invention;

FIG. 4 is a block diagram of a component library verification system provided by another optional embodiment of the present invention;

Fig. 5 is a block diagram of a component library verification device provided by another optional embodiment of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

The embodiment of the present invention provides a component library verification method, as shown in Figure 1, the component library verification method includes:

S101. Obtain the storage address of the target component library input by the user, and perform information verification on the target component library based on the storage address method.

Optionally, in an optional embodiment of the present invention, the above-mentioned construction process of the target component library may be that the developer creates an initial component library based on a computer programming language (Ruby) to create a sub-library scaffolding command (pod create), and The corresponding function development work is carried out under the sample folder of the initial component library. After the development work is completed, the source code management tool (Git) is used to send the component library with the version number added to the corresponding storage server for storage, thereby completing the construction of the component library.

It should be noted that, in an actual application scenario, the above storage address is a storage path for storing data such as source code and index files of the target component library in the terminal device used by the user. After the target component library is built, the user will access the above storage server according to the address recorded in the index file of the target component library. And download the component library with the version number added and its configuration information from the above storage server to the terminal device used by the user, so as to perform the subsequent verification steps.

It should be noted that, in an actual application scenario, the above information verification may be an operation of verifying information such as the version, configuration, and dependency of the component library. Since the component library may be adjusted or modified many times during the development and debugging process, when storing the component library and its related information, there may be errors in storing the modified component library to the storage address of the component library before modification risks of. Therefore, through the above step S101 as shown in FIG. 1 , the risk of component library verification failure due to the inconsistency between the version or configuration of the component library stored in the storage address and the version or configuration of the target component library to be released can be avoided.

S102. Obtain a component library verification instruction input by the user when the content of the verification result of the information verification is that the verification is passed.

It should be noted that, in actual application scenarios, there may be multiple types of component library verification instructions for obtaining user input, and one is provided here as an example:

When it is detected that the content of the verification result of the information verification is verified, the command input interface is displayed by calling the built-in command line terminal tool (Terminal) of the iOS system. A schematic diagram of the command input interface is shown in FIG. 2 . The command input interface is composed of a command input box and command prompt information. Wherein, the command prompt information is an example for respectively prompting the corresponding command of the verification step, for example, the command Step0 corresponds to the exit process, the command Step1 corresponds to the local verification, the command Step2 corresponds to the remote verification, and the command Step3 corresponds to the version verification.

Optionally, in an optional embodiment of the present invention, the above-mentioned component library verification instruction can be executed separately, or after the component library verification instruction is executed, automatically trigger the verification step corresponding to the component library verification instruction a verification step.

S103. Identify the verification type of the component library verification instruction, call a preset verification instruction group corresponding to the verification type, verify the target component library, and output a verification result.

It should be noted that, in an actual application scenario, the verification type of the above-mentioned component library verification instruction represents a component library verification step corresponding to the component library verification instruction.

Those skilled in the art can understand that, in an actual application scenario, the above specific implementation manner of invoking the preset verification command group corresponding to the verification type can be realized by calling the built-in shell command function of the iOS system. The present invention does not give too many details on the specific calling method of the above-mentioned shell command function.

Optionally, in an optional embodiment of the present invention, the above-mentioned preset verification instruction group may be data composed of a plurality of standard instructions required for executing each verification step of the component library, and the call and trigger relationship of the instructions Group. After the preset instruction group corresponding to the verification type is determined, the preset instruction group will automatically call a plurality of standard instructions in the preset instruction group according to the above call and trigger relationship, and perform corresponding verification operations on the target component library. Wherein, the above-mentioned standard instructions refer to built-in instructions provided by the source code management tool.

It should be noted that in actual application scenarios, in order to fully verify the component library, the existing technology requires developers or testers to manually input built-in instructions provided by source code management tools. However, with the increase in the functional complexity of the component library and the number of referenced open source source codes, the number of built-in commands that need to be called to verify the component library and the complexity of the relationship between commands also increase. This makes it impossible for users who have a low level of mastery of source code management tools to accurately call a large number of built-in commands to efficiently and accurately verify the component library. At the same time, since the accuracy of user-developed auxiliary commands is easily affected by the developer's mastery of source code management tool commands, the reliability and efficiency of component library verification using auxiliary commands will also be affected. Therefore, the present invention establishes a preset instruction group that can be automatically run, and establishes the corresponding relationship between the verification type of the component library verification instruction and the preset verification instruction group, so that the user does not need to learn and understand the huge built-in instructions of the source code management tool. Complete verification of the target component library can be achieved simply by entering the component library verification instructions corresponding to the verification steps that need to be performed. Improved reliability and efficiency of verification of component libraries.

The present invention checks the information of the target component library based on the storage address input by the user, which can avoid the inconsistency between the version or configuration of the component library stored in the storage address and the version or configuration of the target component to be released and the release of the component library. The risk method that causes component library verification to fail, thereby reducing verification efficiency. Moreover, by establishing a preset instruction group that can be automatically run, and establishing the corresponding relationship between the verification type of the component library verification instruction and the preset verification instruction group, users do not need to learn and understand the huge built-in instructions of the source code management tool. Inputting the component library verification instruction corresponding to the verification steps to be performed can automatically realize the comprehensive verification of the target component library. Improved verification efficiency for component libraries. It can be seen that the present invention improves the verification efficiency of the component library.

Optionally, the verification type of the component library verification instruction is identified above, and a preset verification instruction group corresponding to the verification type is called to verify the target component library and output a verification result, including:

Use the preset string matching algorithm to identify the component library verification instruction and obtain the verification type;

Determining a verification instruction group identifier corresponding to the verification type;

Call the preset verification command group with the verification command group identifier to verify the target component library and output the verification result.

Those skilled in the art can understand that, in actual application scenarios, the types of the above-mentioned preset string matching algorithms can be various, such as suffix matching (Boyer-Moore, BM) algorithm, violent retrieval matching (Brute Force, BF) algorithm, hash retrieval matching (Robin-Karp, RK) algorithm, etc. Moreover, the method of invoking the preset character string matching algorithm described above is a well-known technique for those skilled in the art. The present invention does not give too many details on the specific types and calling methods of the above-mentioned preset character string matching algorithm.

Optionally, obtain the storage address of the target component library input by the user, and perform information verification on the target component library based on the storage address, including:

Obtain the storage address of the target component library input by the user, access the storage address, and determine whether the file data whose data type is an index file is stored in the storage address;

In the case of storing file data in the storage address, judge whether the target component library is stored in the storage address, if so, read the version number and configuration information of the target component library in the file data, and judge the version number and the target component library Check whether the version label is consistent, and judge whether the source code information in the target component library is consistent with the configuration information;

When the version number is consistent with the version label, and the source code information is consistent with the configuration information, the output content is the verification result of the information verification that passed the verification.

Optionally, in an optional embodiment of the present invention, multiple types of information such as the version number, configuration information, and dependent library information of the corresponding component library can be constructed, stored, and published in the above-mentioned index file. After the user method finds the storage address of the target component library corresponding to the index file according to the index file, if there is no problem of uploading the wrong version of the component library or the wrong storage address of the component library, then the storage address should store the target component library and its corresponding index file, and the information about the component library recorded in the index file is consistent with the information of the target component library. The present invention can improve the reliability of component library verification through the above information verification.

Optionally, in another optional embodiment of the present invention, the above-mentioned specific implementation manner of judging whether file data whose data type is an index file is stored in the storage address may be: read each file data in the storage location File name suffix, to determine whether there is a file name suffix with the suffix ".podspec" in each file name suffix. If it exists, it is determined that file data whose data type is an index file is stored in the storage address.

Those skilled in the art can understand that, the above-mentioned operation steps of information verification can be realized through the file query function of Python language. The present invention does not give too many details on the specific implementation process.

It should be noted that, in the actual application scenario, the operation steps for judging whether the version number is consistent with the version label of the target component library and whether the source code information in the target component library is consistent with the configuration information can be determined in the above judgment storage address The operation step of whether the file data whose data type is an index file is stored is executed after, or it can be executed before the operation step of verifying the target component library described below.

Optionally, in the case that the verification instruction identifier includes an identifier for local verification, call the preset verification instruction group with the verification instruction group identifier, verify the target component library, and output the verification result, including:

Invoke the preset verification instruction group with the verification instruction group identification that represents the identification for local verification, read the dependent library information of the target component library, and obtain the storage address of the dependent source code;

Obtain the dependent source code stored in the storage address of the dependent source code, and compile the dependent source code locally;

In the case that the local compilation of the dependent source code is successful, it is determined that the local verification of the target component library is passed, and the content is output as a verification result of passing the verification.

Those skilled in the art can understand that, in the actual application scenario, the above-mentioned step of reading the dependent library information of the target component library and obtaining the storage address of the dependent source code can be built and provided by the source code management builder for local verification command (pod lib lint) to trigger.

Optionally, in the case that the verification instruction identifier includes an identifier for remote verification, call the preset verification instruction group with the verification instruction group identifier, verify the target component library, and output the verification result, including:

Invoke the preset verification instruction group with the verification instruction group identifier representing the identification for remote verification, obtain the index file stored in the storage address, and obtain the source code data of the target component library according to the source code remote storage address in the index file;

Compile the source code data locally. If the local compilation is successful, it is determined that the remote verification of the target component library has passed, and the output content is the verification result of the verification.

Those skilled in the art can understand that, in the actual application scenario, the above-mentioned reading obtains the source code data of the target component library according to the source code remote storage address in the index file, and the local and remote verification instructions provided by the source code manager (pod lib lint) to trigger.

Optionally, in the case that the verification instruction identifier includes an identifier for version verification, call the preset verification instruction group with the verification instruction group identifier, verify the target component library, and output the verification result, including:

Invoke the preset verification instruction group with the identification of the verification instruction group for version verification, obtain the index file stored in the storage address, and obtain the target version component library according to the remote storage address of the version in the index file;

Compile the component library of the target version locally. If the local compilation is successful, it is determined that the version of the component library of the target version has passed the verification, and the output content is the verification result of the verification.

Those skilled in the art can understand that, in the actual application scenario, the above-mentioned reading obtains the source code data of the target component library according to the source code remote storage address in the index file, and can pass the push verification instruction (pod repo push) provided by the source code manager to trigger.

Those skilled in the art can understand that, in actual application scenarios, the above local compilation process consists of preprocessing, compiling, assembling and linking operations. It can be realized through the automatic building and packaging command (Xcodebuild) provided by the MAC system. In the present invention, the specific implementation process will not be described in detail.

Optionally, the above component library verification method as shown in Figure 1 also includes:

When the content of the verification result is that the verification is passed and the command to publish the component library is received, the build will issue a component library publishing command to send the index file of the target component library to the target remote method file index warehouse input by the user. The storage area corresponding to the address is stored, and the release of the target component library is completed.

Those skilled in the art can understand that, in an actual application scenario, the release of the above component library can also be implemented through the above push verification instruction (pod repo push).

It should be noted that, in an actual application scenario, the above-mentioned operation of the user inputting the address of the target remote file index warehouse (specs git) can be performed after the execution of step S102 as shown in FIG. Execute after the step S103 shown is completed. The present invention does not place too many restrictions on the execution sequence of the above-mentioned operation steps in which the user inputs the address of the target remote file index warehouse.

It should be noted that, in an actual application scenario, there are many ways to execute the component library verification method shown in Figure 1, and one is provided as an example here:

As shown in Figure 3, it is a flow chart of a component library verification method, and its specific process includes:

Step S301, obtaining the storage address of the target component library input by the user. And trigger step S302.

Step S302, judging whether the target component library passes the information verification based on the storage address. If yes, trigger step S303. If not, repeat step S301.

Optionally, in an optional embodiment of the present invention, when the target component library fails the information verification, step S301 may be performed after an error pop-up window pops up.

In step S303, an instruction input box is displayed, and a component library verification instruction input by the user is obtained. And trigger step S304.

Step S304, judging whether the verification type of the component library verification instruction is the exit verification type. If yes, trigger step S308. If not, step S305 is triggered.

Step S305, judging whether the verification type of the component library verification instruction is a local verification type. If yes, trigger step S309. If not, step S306 is triggered.

Step S306, judging whether the verification type of the component library verification instruction is a remote verification type. If yes, step S310 is triggered. If not, step S307 is triggered.

Step S307, judging whether the verification type of the component library verification instruction is a version verification type. If yes, step S311 is triggered. If not, return to step S303.

It should be noted that the execution sequence of steps S304 to S307 shown in FIG. 3 is constructed and published for demonstration purposes. For the specific component library verification steps and the names of each step, they can be set according to the actual method application scene, and the present invention does not make too many limitations and repeat them.

It should be noted that, the execution sequence of step S304 to step S307 as shown in FIG. 3 is only for demonstration and description. In an actual application scenario, at least one type verification step in the above steps S304 to S307 can be performed according to the component library verification instruction input by the user in step S303, or each type can be executed sequentially according to the execution sequence shown in Figure 3 Verification steps.

Optionally, in another optional embodiment of the present invention, in the case that the verification type of the component library verification instruction is not the version verification type, it is possible to return to step S303 after an error pop-up window pops up.

Step S308, end the process.

Step S309, call a preset verification command group corresponding to the local verification type, and perform a local verification operation on the target component library. And trigger step S312.

Step S310, call a preset verification instruction group corresponding to the remote verification type, and perform a remote verification operation on the target component library. And trigger step S312.

Step S311, call a preset verification instruction group corresponding to the version verification type, and perform a version verification operation on the target component library. And trigger step S312.

Step S312, displaying the verification result. And trigger step S308.

It should be noted that the above steps S301 and S302 shown in FIG. 3 are optional embodiments of step S101 shown in FIG. 1 . The above step S303 shown in FIG. 3 is an optional embodiment of step S102 shown in FIG. 1 . The above step S304 to step S312 shown in FIG. 3 are optional embodiments of step S103 shown in FIG. 1 .

Corresponding to the above method embodiments, the present invention also provides a component library verification system, as shown in Figure 4, the component library verification system includes:

An information verification module 401, configured to obtain the storage address of the target component library input by the user, and perform information verification on the target component library based on the storage address;

The instruction obtaining module 402 is used to obtain the component library verification instruction input by the user when the content of the verification result of the information verification is verified;

The verification module 403 is used to identify the verification type of the component library verification instruction, construct and use a preset verification instruction group corresponding to the verification type, verify the target component library, and output the verification method result.

Optionally, the above verification module 403 is set to:

Use the preset string matching algorithm to identify the component library verification instruction and obtain the verification type;

Determining a verification instruction group identifier corresponding to the verification type;

Call the preset verification command group with the verification command group identifier to verify the target component library and output the verification result.

Optionally, the above information verification module 401 is set to:

Obtain the storage address of the target component library input by the user, access the storage address, and determine whether the file data whose data type is an index file is stored in the storage address;

In the case of storing file data in the storage address, judge whether the target component library is stored in the storage address, if so, read the version number and configuration information of the target component library in the file data, and judge the version number and the target component library Check whether the version label is consistent, and judge whether the source code information in the target component library is consistent with the configuration information;

When the version number is consistent with the version label, and the source code information is consistent with the configuration information, the output content is the verification result of the information verification that passed the verification.

Optionally, the above verification module 403 is specifically configured as:

In the case that the verification instruction identifier includes the identifier for local verification, call the preset verification instruction group with the verification instruction group identifier for the identifier for local verification, read the dependent library information of the target component library, and obtain the storage of the dependent source code address;

Obtain the dependent source code stored in the storage address of the dependent source code, and compile the dependent source code locally;

In the case that the local compilation of the dependent source code is successful, it is determined that the local verification of the target component library is passed, and the content is output as a verification result of passing the verification.

Optionally, the above verification module 403 is specifically configured as:

In the case that the verification instruction identifier includes an identifier for remote verification, call the preset verification instruction group with the verification instruction group identifier for the identifier for remote verification, obtain the index file stored in the storage address, and according to the index file in the index file The remote storage address of the source code to obtain the source code distribution data of the target component building library;

Compile the source code data locally. If the local compilation is successful, it is determined that the remote verification of the target component library has passed, and the output content is the verification result of the verification.

Optionally, the above verification module 403 is specifically configured as:

In the case that the verification command identification includes the identification of version verification by characterizing, call the preset verification command group with the verification command group logo of character verification to obtain the index file stored in the storage address, and remotely according to the version in the index file The storage address obtains the component library of the target version;

Compile the component library of the target version locally. If the local compilation is successful, it is determined that the version of the component library of the target version has passed the verification, and the output content is the verification result of the verification.

Optionally, the above component library verification system as shown in Figure 4 also includes:

The release module is used to call the component library release command to send the index file of the target component library to the target remote file index warehouse address corresponding to the input of the user when the content of the verification result is verified and the component library release command is received. storage area to complete the release of the target component library.

The embodiment of the present invention also provides a component library verification device, as shown in Figure 5, the component library verification device includes:

Processor 501;

A memory 502 for storing instructions executable by the processor 501;

Wherein, the processor 501 is configured to execute instructions, so as to implement any one of the component library verification methods described above.

The embodiment of the present invention also provides a computer-readable storage medium. When the instructions in the computer-readable storage medium are executed by the processor of the component library verification device, the component library verification device can execute any one of the above-mentioned component libraries. Authentication method.

In a typical configuration, a device includes one or more processors (CPUs), memory and a bus. A device may also include input/output interfaces, network interfaces, and the like.

Memory may include non-permanent memory in computer-readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM), memory includes at least one memory chip. The memory is an example of a computer readable medium.

Computer readable media includes both volatile and non-permanent, removable and non-removable media methods and may be implemented by any method or technology for storage of information. Information may be computer readable commands, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridge, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems or computer program products. Accordingly, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is a relationship between these entities or operations. There is no such actual relationship or order between them. It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes Other elements not expressly listed, or elements inherent in the process, method, commodity, or apparatus are also included. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

Each embodiment in this specification is described in a related manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for relevant parts, refer to part of the description of the method embodiment.

The above are only examples of the present application, and are not intended to limit the present application. For those skilled in the art, various modifications and changes may occur in this application. All modifications, equivalent replacements, improvements, etc. built and released within the spirit and principle of the application shall be included within the scope of the claims of the application.

Claims (10)

1. A component library verification method is characterized in that, the method comprises: method Obtaining the storage address of the target component library input by the user, and performing information verification on the target component library based on the storage address; If the content of the verification result of the information verification is that the verification is passed, obtain a component library verification instruction input by the user; Identifying the verification type of the component library verification instruction, calling a preset verification instruction group corresponding to the verification type, verifying the target component library, and outputting a verification result. 2. The method according to claim 1, wherein the verification type of the verification instruction of the component library is identified, and a preset verification instruction group corresponding to the verification type is called, and the target component The library performs verification and outputs verification results, including: Using a preset character string matching algorithm to identify the component library verification instruction to obtain the verification type; Determining a verification instruction group identifier corresponding to the verification type; Invoke the preset verification instruction group with the verification instruction group identifier, verify the target component library, and output the verification result. 3. The method according to claim 1, wherein the obtaining the storage address of the target component library input by the user, and performing information verification on the target component library based on the storage address comprises: Obtaining the storage address of the target component library input by the user, accessing the storage address, and judging whether file data whose data type is an index file is stored in the storage address; In the case where the file data is stored in the storage address, determine whether the target component library is stored in the storage address, if so, read the version number of the target component library in the file data and configuration information, judging whether the version number is consistent with the version label of the target component library, and judging whether the source code information in the target component library is consistent with the configuration information; When the version number is consistent with the version label, and the source code information is consistent with the configuration information, the output content is a verification result of the information verification that passes the verification. 4. The method according to claim 2, characterized in that, in the case that the verification instruction identifier includes an identifier for performing local verification, the call has the construction and pre-issued configuration of the verification instruction group identifier The verification instruction group verifies the target component library and outputs verification results, including: method Invoking the preset verification instruction group with the verification instruction group identifier representing the identifier for the local verification, reading the dependent library information of the target component library, and obtaining the storage address of the dependent source code; Obtaining the dependent source code stored in the storage address of the dependent source code, and locally compiling the dependent source code; If the local compilation of the dependent source code is successful, it is determined that the local verification of the target component library is passed, and the verification result that the verification is passed is output. 5. The method according to claim 2, characterized in that, in the case where the verification instruction identifier includes an identifier for remote verification, the call has a preset verification instruction group with the verification instruction group identifier, for The target component library performs verification and outputs verification results, including: Invoking the preset verification instruction group with the verification instruction group identifier representing the identifier for the remote verification, obtaining the index file stored in the storage address, and remotely storing the address according to the source code in the index file, Obtaining source code data of the target component library; Perform local compilation on the source code data, and if the local compilation is successful, determine that the remote verification of the target component library has passed, and output the verification result whose content is that the verification has passed. 6. The method according to claim 2, characterized in that, in the case where the verification instruction identifier includes an identifier that represents a version verification, the call has a preset verification instruction group with the verification instruction group identifier, for The target component library performs verification and outputs verification results, including: Invoke the preset verification instruction group with the identification of the verification instruction group for the version verification, obtain the index file stored in the storage address, and obtain the target version according to the remote storage address of the version in the index file component library; The local compilation is performed on the target version component library, and if the local compilation is successful, it is determined that the version verification of the target component library is passed, and the verification result is output as the verification result. 7. The method according to claim 1, further comprising: When the content of the verification result is that the verification is passed, and the release component library instruction is received, the component library release command is invoked, and the index file of the target component library is sent to the user-input build and target release remote The storage area corresponding to the address of the file index warehouse is stored to complete the release of the target component method library method. 8. A component library verification system, characterized in that the system comprises: An information verification module, configured to obtain the storage address of the target component library input by the user, and perform information verification on the target component library based on the storage address; An instruction obtaining module, configured to obtain the component library verification instruction input by the user when the content of the verification result of the information verification is verified; The verification module is configured to identify the verification type of the verification instruction of the component library, call a preset verification instruction group corresponding to the verification type, verify the target component library, and output a verification result. 9. A component library verification device, characterized in that the device comprises: processor; memory for storing said processor-executable instructions; Wherein, the processor is configured to execute instructions to implement the component library verification method according to any one of claims 1-7. 10. A computer-readable storage medium, characterized in that, when the instructions in the computer-readable storage medium are executed by the processor of the component library verification device, the component library verification device is able to perform the tasks described in claims 1 to 10. The component library verification method described in any one of 7.

Images