Skip to content
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

composer diagnose should also check for missing/modified files in packages #8040

Closed
connorshea opened this Issue Mar 14, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@connorshea
Copy link

connorshea commented Mar 14, 2019

I recently had a problem with a package acting incorrectly that took almost an hour to solve because composer diagnose didn't warn me about a package having been modified. (In hindsight, obviously one of the first things I should have done was delete the vendor/ directory and reinstall, but I didn't because I'm a dummy.)

If you modify or delete a file in a package and then run composer diagnose, it won't point out any problem with your current setup. So I ended up going on a wild goose chase trying to figure out the problem.

I know composer status exists and does this (well, I know now), but diagnose seems to me like it should also check for things like that. At the least, it'd be nice if – at the end of composer diagnose – it told the user about the existence of composer status as a possible way to detect problems.

Thanks for composer, it's worked quite well so far other than that :)

@alcohol

This comment has been minimized.

Copy link
Member

alcohol commented Mar 15, 2019

diagnose is meant to verify your Composer configuration and setup. It it not meant to verify your vendor contents.

@alcohol alcohol closed this Mar 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.