Repository navigation
Fix Composer development autoload metadata - #57
Merged
Merged
Conversation
Contributor
|
It would also be nice if tests had |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What changed
autoload-devsection for the test suite.Why
The package already separates PHPUnit into
require-dev, but its test classes were not declared in Composer's development autoload metadata. Declaringtests/as a development-only classmap makes the Composer metadata explicit and avoids treating test code as production autoloadable code.Validation
The existing GitHub Actions workflow runs
composer validate --strict, installs dependencies, and executes the test suite across PHP 8.0–8.6.