| Server IP : 199.250.214.225 / Your IP : 52.14.195.161 Web Server : Apache System : Linux vps64074.inmotionhosting.com 3.10.0-1160.105.1.vz7.214.3 #1 SMP Tue Jan 9 19:45:01 MSK 2024 x86_64 User : nicngo5 ( 1001) PHP Version : 7.4.33 Disable Function : exec,passthru,shell_exec,system MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : OFF Directory : /home/nicngo5/grp.nicn.gov.ng/vendor/league/flysystem/ |
Upload File : |
# Deprecations This document lists all the planned deprecations. ## Handlers will be removed in 2.0 The `Handler` type and associated calls will be removed in version 2.0. ### Upgrade path You should create your own implementation for handling OOP usage, but it's recommended to move away from using an OOP-style wrapper entirely. The reason for this is that it's too easy for implementation details (for your application this is Flysystem) to leak into the application. The most important part for Flysystem is that it improves portability and creates a solid boundary between your application core and the infrastructure you use. The OOP-style handling breaks this principle, therefore I want to stop promoting it.