The functionality of our App is divided into multiple feature modules that are lazily loaded. Each module is loaded under different path matches, and some modules import a shared module containing reusable components. Everything seems to be working well so far.
Now, we have encountered a situation where both module-A and module-B are using the same shared module with a component that emits outputs triggering routing navigation. Module-A wants to trigger a routing on a deeper nested path than what is configured for module-B. We can call the router navigate with the specific path to module-B to make everything function properly.
However, it feels strange to allow one domain (module-A) to have knowledge of the routing configuration details of another domain (module-B). Are there any suggestions on how to keep the routing configuration in module-B confidential so that module-A does not access the routing information from module-B?
Is this clear? I hope so, thank you! :)