Actions
Bug #69270
closed
Cleanup navigation frame module registration
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend API
Target version:
-
Start date:
2015-08-23
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
http://review.typo3.org/37611 made the navigation frame dispatched.
For this it leveraged the addNavigationComponent API,
which was introduced only for ExtJS tree components.
Since we want to get rid of ExtJS (and this API specifically),
we need to introduce a different way to make modules or routes
navigation components.
This change reverts the above changes to the API and instead uses the `navigationFrameModule`
option which was introduced in https://review.typo3.org/#/c/30593
To make this option work with top level modules and inheritance of the navigation frame,
the evaluation of the option is moved to the module loader, which has the benefit to
have the code only in one place while it needed to be in two places before.
Updated by 
Updated by 
Updated by
Actions