You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
32 lines
1.3 KiB
32 lines
1.3 KiB
<?php |
|
|
|
declare( strict_types=1 ); |
|
|
|
use Isolated\Symfony\Component\Finder\Finder; |
|
|
|
return array( |
|
|
|
/* |
|
* By default when running php-scoper add-prefix, it will prefix all relevant code found in the current working |
|
* directory. You can however define which files should be scoped by defining a collection of Finders in the |
|
* following configuration key. |
|
* |
|
* For more see: https://github.com/humbug/php-scoper#finders-and-paths |
|
*/ |
|
'finders' => [ |
|
Finder::create()->files()->in( 'vendor/psr/container' )->name( [ '*.php', 'LICENSE', 'composer.json' ] ), |
|
Finder::create()->files()->in( 'vendor/psr/http-message' )->name( [ '*.php', 'LICENSE', 'composer.json' ] ), |
|
Finder::create()->files()->in( 'vendor/psr/log' )->exclude( 'Test' )->name( [ '*.php', 'LICENSE', 'composer.json' ] ), |
|
], |
|
|
|
/* |
|
* When scoping PHP files, there will be scenarios where some of the code being scoped indirectly references the |
|
* original namespace. These will include, for example, strings or string manipulations. PHP-Scoper has limited |
|
* support for prefixing such strings. To circumvent that, you can define patchers to manipulate the file to your |
|
* heart contents. |
|
* |
|
* For more see: https://github.com/humbug/php-scoper#patchers |
|
*/ |
|
'patchers' => [], |
|
|
|
);
|
|
|