feat: moon check single package(and it's deps)

[Young-Flash]

No description provided.

[peter-jerry-ye-code-review]

Identified Issues and Suggestions

1. Potential Bug: Unused Variable check_opt in run_check_internal

   • In the run_check_internal function, the check_opt variable is assigned but never used directly within the function. This could indicate that the intended functionality related to check_opt is not being executed or tested.
   • Suggestion: Ensure that all options specified in CheckOpt are being utilized appropriately within the function. This might involve adding logic to handle the package_path, patch_file, and no_mi options effectively.

2. Potential Bug: Incorrect Error Message in debug_flag_test

   • The error message displayed in the debug_flag_test function seems to incorrectly indicate the usage of the check command. The message suggests that the command is moon check --release but the actual usage should be moon check --release [PACKAGE_PATH] as per the updated command structure.
   • Suggestion: Update the expected error message in the test to correctly reflect the current usage of the check command, including the optional PACKAGE_PATH argument.

3. Documentation Update: Command Usage for moon check

   • The documentation for the moon check command in both English (docs/manual/src/commands.md) and Chinese (docs/manual-zh/src/commands.md) versions should be updated to include the new PACKAGE_PATH argument and the associated options (--patch-file and --no-mi).
   • Suggestion: Update the usage section of the moon check command to include the PACKAGE_PATH argument and clearly describe the conditions under which --patch-file and --no-mi options are valid.

Additional Observations

• Code Duplication: There is noticeable duplication in the handling of patch_file and no_mi options across different functions (pkg_to_check_item, pkg_with_wbtest_to_check_item, pkg_with_test_to_check_item). This could be refactored to reduce redundancy.
• Incomplete Implementation: The functionality to filter packages based on package_path in gen_check seems partially implemented. The logic to handle patch_file and no_mi options for specific packages needs to be thoroughly tested and possibly refined.

Conclusion

The provided diff shows several additions and modifications related to enhancing the check command functionality, particularly around specifying packages for checking and handling patch files. However, there are areas where the implementation and documentation need to be aligned to ensure that the new features are fully functional and clearly understood by users. Addressing the identified issues and suggestions will help in improving the robustness and clarity of the code and documentation.