Feature #37
AOP: Test introducing multiple interfaces
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Robert Lemke | % Done: | 0% |
|
| Category: | AOP | |||
| Target version: | TYPO3 Flow Base Distribution - 0.1 | |||
| PHP Version: | Complexity: | |||
| Has patch: |
Description
Some more tests need to be written to test introduction of more than one interface and what happens if interfaces have conflicting method signatures.
History
#1 Updated by Robert Lemke over 8 years ago
- Status changed from New to Closed
- Sprint set to fixed
(In r167) Refactored the T3P_Core_AOPProxyClassBuilder:
- Core: The AOPProxyClassBuilder smelled like Duplicated Code (76) and therefore I decided to split it up using the Template Method (325) pattern. Addresses #35.
- Core: Added tests and fixtures to assert that introducing multiple interfaces does work (it didn't work as my tests showed soon). Now everything seems to be fine and that fixes #37.