-
-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add a info:requirements command #1273
base: main
Are you sure you want to change the base?
Conversation
This is a preparatory step for #1273. The goal is to be able to provide _all_ the requirements. The idea being that one may be interested in seeing this full list for debugging purpose, rather than the strict final one where the provided extensions removed the required extensions from the calculated requirements.
@llaville any opinion regarding the output? (you can also check the text output in the tests) |
Hello @theofidry After :
I run test on commit
First use case : run
Then I tried unit tests with
|
@llaville That the unit tests were failing was expected (in the sense the CI was failing too), but the error you have should already be fixed (there is a string cast at the very failing statement that you have). I extracted it in #1335 for better visibility (I originally kind of expected this issue when extracted it in #1334 but I did not have a failing case at that time) |
@theofidry Thanks for the fix, it run better now ! info:requirements on PHPLint 9.1[email protected] in /shared/backups/github/box-fidry $ bin/box info:req -d /shared/backups/github/phplint/
Now on improvement, what I'd like to have : For a better readability on extension report used (sort results by type column)
And the best one will be to add, as I've already explained, the note about
|
is it really better to sort by source rather than extension? Because if you want to evaluate why there is an extension or not that it what you would need |
I'll rename it to |
Related to #1237.