Nested mapping

[jhabaj]

• new feature
• BC break? no - generally fully backward compatible, though some applications may have specific edge cases
• doc PR: nette/docs#???

This pull request introduces an enhancement to the presenter mapping functionality, allowing support for mappings within multiple namespaces.

Currently, adding a new app module requires specifying mappings like this:

'ForumModule' => 'Other\*Mod\*Presenter';
Applications such as CMS systems must carefully manage link generation between frontend and admin modules, ensuring routes are correct for each.

Proposed Solution:
The proposal enables nested mapping, simplifying the creation of links using only the module name and presenter. It eliminates the need to create separate routes for each module.

'Admin' => 'App\*Mod\*Presenter',
'Admin:ForumModule' => 'Other\*Mod\*Presenter',
'Admin:Module:ForumModule' => 'Other\*Mod\*Presenter', // Length is customizable based on application needs

Benefits

• Improved Modularity: Each module can function as an independent composer package, extending shared presenters and integrating seamlessly into the application.
• Streamlined Link Generation: Linking becomes more intuitive, relying on the module name and presenter alone.
• Plugin System Potential: Applications can adopt a plugin-like structure, where modules extend common functionality and are easily reusable.
• This change aims to make Nette applications more flexible and modular, reducing the overhead of managing complex routing setups while supporting scalable, pluggable architectures.