Lukas Kahwe Smith
Lukas Kahwe Smith
https://github.com/KnpLabs/KnpMenu/pull/161 seems to be addressing this for 2.1
Ah ok I get it now. So as part of building the menu graph, KnpMenu will need to generate the uri etc of all nodes that could possibly appear in...
well i think there will be cases where its needed. however 1) it should be an option 2) it should stop reading once it has found something .. right now...
were the underlying issues for this addressed in KnpMenu 2.0.0? @Nek- @stof ?
@Nek- no, though this might help. with KnpMenu 1.x even if you specified a depth, it still read the entire tree to render. ie. ``` knp_menu_render(' AcmeDemoBundle:Builder:mainMenu', {'depth': 2, 'currentAsLink':...
orderability of children is a node type feature. it is enabled by default, though it can have a severe impact on performance (but only if you go into the thousands...
right now we support changes to the order via the TreeBrowserBundle where you can change the order via drag and drop.
i don't think we should cascade. i fear this maybe need a checkbox or something to manually trigger the cascade.
I think its a great idea .. the question is the timing. I was about to go to RC1 with the MediaBundle this Wednesday :) So either we: 1) rush...
@havvg do you maybe have an idea here?