Autoload relative paths first to avoid confusion with files from the global include path #2751
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.
Problem: autoload files are confused with globally available files. See pfrenssen/coder#54
If you specify
<autoload>./autoload.php</autoload>
in your ruleset.xml file then a completely different autoload.php file from your system might be executed, even although you specified a relative path.Steps to reproduce:
composer install
./vendor/bin/phpcs --standard=./standard test.php
Output:
PHP Parse error: syntax error, unexpected 'invalid' (T_STRING) in test_phpcs/autoload.php on line 3
Which means the wrong autoload.php file was included.
Proposed solution: Try to include relative paths first, then try global paths.
Not sure how we can test this, any tips for that?