Make Eel usable outside of TYPO3 Flow
There is not much coupling to the Flow framework in Eel. To make it usable for any PHP project we have to remove TYPO3 Flow base classes and provide interfaces for tightly coupled implementations.
After a first analysis I figured out the following todos:
- Implement standalone ObjectAccess for
PropertyOperation(getPropertyInternal and getPropertyPath)
- Don't extend
Packageclass and move Regexp to other type (e.g.
- Provide an
OperationResolverInterfaceand provide a non-Flow implementation (e.g. simple array configuration of operations)
- Don't use
UnitTestCasefor unit test cases, think about way of removing
This should be everything to make the whole package usable without Flow and remove the composer dependency.
No data to display