Task #42240
Make Eel usable outside of TYPO3 Flow
Status: | New | Start date: | 2012-10-21 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | - |
Description
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
Context
andPropertyOperation
(getPropertyInternal and getPropertyPath) - Don't extend
TYPO3\Flow\Exception
in exceptions - Remove
Package
class and move Regexp to other type (e.g.EelEvaluatorInterface
) - Provide an
OperationResolverInterface
and provide a non-Flow implementation (e.g. simple array configuration of operations) - Don't use
UnitTestCase
for unit test cases, think about way of removinggetAccessibleMock
This should be everything to make the whole package usable without Flow and remove the composer dependency.