Server IP : 172.67.158.161 / Your IP : 18.225.92.116 Web Server : LiteSpeed System : Linux business53.web-hosting.com 4.18.0-553.lve.el8.x86_64 #1 SMP Mon May 27 15:27:34 UTC 2024 x86_64 User : giankuin ( 1871) PHP Version : 7.4.33 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /proc/thread-self/root/home/giankuin/sieuthiweb.com.vn/wp-content/plugins/wordpress-seo/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' => array( Finder::create()->files()->in( 'vendor/j4mie/idiorm' )->name( [ 'idiorm.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' => array(), /* * By default, PHP-Scoper will not prefix the user defined constants, classes and functions belonging to the global * namespace. You can however change that setting for them to be prefixed as usual unless explicitly whitelisted. * * https://github.com/humbug/php-scoper#whitelist */ 'whitelist-global-classes' => false, );