Tiago Neves wrote:
Clever answer Tiago, however, this will likely end in circular references due to the other modules using the "menu" WebBlock in this module, and this module using the others' WebScreens references.
The approach I suggested was for the use case that jason mentioned (see below), which doesn't imply any circular references.
What you are referring to on your post is a different thing and would of course lead to circular references which could be avoided with links to External URL - however that would be a last resort for me... It all depends on what you are trying to achieve and if you plan ahead your architecture the right way.
jason Kilkenny wrote:
I'm also having issues with this. I want my menu to be transversal through the entire application, where each menu entry allows me to navigate to another module. I want to do this because each module is quite complex and I want the developers to be distributed among modules.
I have tried the public screens option but yes, it does create circular references, so it is not an option for me.
I can use external urls, but how do I dinamically get the URL? In the same module I know that I can use the
function, but I am not able to make the Entry points public in different webflows so that I can use them in different modules, right?
Any ideas on this?
Thanks in advance,