-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Run composer validate from different commands #7492
Comments
If you wanna do more why not as long as it doesn't nag people needlessly.. I don't think this problem occurs that often tbh but obviously it's hard to tell. |
is this LAX validation done, because of performance problems or do not all operations require a strict schema?
in the regular used commands like composer install/update I would only add this additional check in case of errors, so the regular happy path shouldn't see any more errors/warnings then before. at least this would be the goal. |
Lax just means this:
So we don't check for typo in top level property names, and we don't force name to be present. It's not that big a difference. |
note that |
Closing as IMO doing a full validate is probably overkill, but we have narrowed down the schema quite a bit, and do validate composer.json + auth.json now, and also load the root package with a validating array loader which does 90% of validate command stuff. |
Thanks 🙏 |
As discussed in #5940 (comment) I would like to propose to internally call „composer validate“ from different commands, which can help/should help to find errors caused by invalid composer.json more easily.
I guess it would help in the following commands:
What do you guys think?
The text was updated successfully, but these errors were encountered: