/
home
/
techb158
/
ileadtechnology.com
/
SSM
/
vendor
/
league
/
flysystem
/
/home/techb158/ileadtechnology.com/SSM/vendor/league/flysystem
mkdir
upload
Name
Size
Mode
Actions
src/
-
0755
rm
composer.json
2433
0644
edit
dl
rm
deprecations.md
724
0644
edit
dl
rm
LICENSE
1063
0644
edit
dl
rm
SECURITY.md
428
0644
edit
dl
rm
Edit:
/home/techb158/ileadtechnology.com/SSM/vendor/league/flysystem/deprecations.md
(724B)
# 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.
Save
cmd:
run