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.

Sign up for GitHub

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

Readme: update composer's behaviour #75

Merged
merged 1 commit into from
Oct 3, 2024
Merged

Readme: update composer's behaviour #75

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ And in such cases, the test may work when executed in standalone run, but fail w
Therefore, having a collision detector in CI might be useful.

## Composer's Ambiguous class resolution
You may have thought that Composer itself is somehow solving this, but that is not true. The only similar check that Composer performs (which results in `Warning: Ambiguous class resolution`) happens when classes collide **inside** the `vendor` path, not in your codebase. Composer does not report class ambiguity in your project at all.
The check that Composer performs (which results in `Warning: Ambiguous class resolution`) [has some weird hidden ignores](https://github.com/composer/composer/issues/12140#issuecomment-2389035210) that makes it generally not usable.

## Supported PHP versions
- PHP 7.2 - PHP 8.3
Expand Down
Loading