Bug #69270
Updated by Helmut Hummel over 8 years ago
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 adds `navigationComponentRoute` and `navigationComponentModule` as new configuration options for modules to either specify a route or a module name as navigation component. http://review.typo3.org/38004 removed the above changes typo3/mod directory with the main modules and their configuration and added the configuration to the `$GLOBALS['TBE_MODULES']`directly. However for that a sub array key `configuration` was used, which is inconsistent with all our current API and instead uses its usages across other modules, leading to the `navigationFrameModule` situation that this configuration option which was basically ignored. On top of that, http://review.typo3.org/39316 introduced the possibility to use sprite icons as module icons, which used the configuration key `icon` in https://review.typo3.org/#/c/30593 the above mentioned sub array key `configuration`, making this key the only option evaluated in the sub array. To make This change removes this option work with top level modules sub array and inheritance of moves the navigation frame, sprite icon configuration on top for consistency. For that the evaluation of key must be changed to 'sprite-icon' as 'icon' was already taken for Extbase module icon configuration. Lastly the option file navigation is moved to routing, using the module loader, which has the benefit to newly introduced API. have the code only in one place while it needed to be in two places before.