|
Server : Apache System : Linux srv.rainic.com 4.18.0-553.47.1.el8_10.x86_64 #1 SMP Wed Apr 2 05:45:37 EDT 2025 x86_64 User : rainic ( 1014) PHP Version : 7.4.33 Disable Function : exec,passthru,shell_exec,system Directory : /home/stando/www/wp-content/plugins/wordpress-seo-premium/config/php-scoper/ |
Upload File : |
<?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' => [], );