Improve user feedback when run without input files (#1969)#2026
Improve user feedback when run without input files (#1969)#2026tmdeveloper007 wants to merge 3 commits intoCCExtractor:masterfrom
Conversation
CCExtractor CI platform finished running the test files on linux. Below is a summary of the test results, when compared to test for commit 2028754...:
Your PR breaks these cases:
Congratulations: Merging this PR would fix the following tests:
It seems that not all tests were passed completely. This is an indication that the output of some files is not as expected (but might be according to you). Check the result page for more info. |
CCExtractor CI platform finished running the test files on windows. Below is a summary of the test results, when compared to test for commit 2028754...:
Your PR breaks these cases:
Congratulations: Merging this PR would fix the following tests:
It seems that not all tests were passed completely. This is an indication that the output of some files is not as expected (but might be according to you). Check the result page for more info. |
|
Closing this PR - the "no input file" handling should be done in Rust (Clap) rather than in the C code. The argument parsing is being migrated to Rust, and Clap provides better facilities for handling this case with proper error messages and help text formatting. Thank you for the contribution effort! |
In raising this pull request, I confirm the following (please check boxes):
My familiarity with the project is as follows (check one):
Improve user feedback when run without input files (#1969)
Summary
This PR improves the command-line feedback provided to users when CCExtractor is executed without any input files. Previously, the tool would dump the entire help screen (hundreds of lines of text), which was confusing for new users and cluttered the terminal.
Changes
EXIT_NO_INPUT_FILESis returned during parameter parsing."Input file required. Run 'ccextractor -h' for help."Why this matters
Clear CLI feedback improves usability for new users and helps avoid confusion when CCExtractor is used in scripts or terminal-based workflows. It aligns with the feedback provided in issue #1969.
Testing Performed
./ccextractorshows the concise error message../ccextractor -hstill displays the full help documentation.