PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` # 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.