Fix autoload configs to avoid warnings when building optimized autoloaders #57275
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The next composer release next week (you can try
composer dump -o
with snapshots right now) warns a bit more about classes which do not match the psr-4 rules they are found in.. Symfony has quite a few false positives there because the rules are using""
as path for all individual components so all files of the component are scanned by default. I already made sure Composer excludes the vendor dir by default now, and this fixes the rest of the errors I noticed.