Skip to content

Suggestion: composer why-not: Better output if package is already installed #12227

@ThomasLandauer

Description

@ThomasLandauer

If I'm doing composer why-not on a package version that I already have, the output is misleading:

$ composer why-not symfony/asset 7.2.0
There is no installed package depending on "symfony/asset" in versions not matching 7.2.0
Not finding what you were looking for? Try calling composer require "symfony/asset:7.2.0" --dry-run to get another view on the problem.

I'm suggesting to replace this with something like:

symfony/asset 7.2.0 is already installed! To find out why, run composer why symfony/asset.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions