Fix autoload configs to avoid warnings when building optimized autoloaders #57275
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fabpot
approved these changes
May 31, 2024
Member
|
Thank you @Seldaek. |
fabpot
added a commit
that referenced
this pull request
Jun 1, 2024
…ized autoloaders (Seldaek) This PR was merged into the 7.1 branch. Discussion ---------- Fix autoload configs to avoid warnings when building optimized autoloaders …aders | Q | A | ------------- | --- | Branch? | 7.1 | Bug fix? | yes | New feature? | no | Deprecations? | no | Issues | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exists, explain below instead --> | License | MIT Same as #57275 but for 7.1 as the new Emoji component also needed a fix. Commits ------- 68f6426 Fix autoload configs to avoid warnings when building optimized autoloaders
This was referenced Jun 2, 2024
Merged
Merged
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 -owith 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.