In case you have special requirements, or your filesystem of choice is not available, you can always create your own adapter.
Every adapter must implement the League\Flysystem\FilesystemAdapter interface. This interface defines all the required methods and lists which exceptions should be thrown in case of a failure.
Testing your adapter is very important. For filesystem adapters, the best tests are integration tests. This means the tests write to the actual filesystems they are providing an interface to.
Although this is more time-consuming to run, this gives the most real guarantees for the consumer of your package.
There is a test package available that allows you to easily test your adapter:
composer require --dev league/flysystem-adapter-test-utilities
Once installed you can use the League\Flysystem\AdapterTestUtilities\FilesystemAdapterTestCase class as your adapter test base-class. This will ensure you’re covering a lot of test scenarios.
The test scenario tests your adapter as a black box, this means it’s designed to perform actual filesystem operations. All of the supported adapters perform actual interactions with the underlying filesystems to provide the most accurate guarantees.
Throwing exceptionsIn order to see which exceptions need to be thrown, checkout the documentation about exceptions.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4