Community
Participate
Working Groups
We need the possibility to set a NavigationArgument not only for the navigate() api, but also for the create() api. With the given patch the interface and implementation is extended. The current NavigationArgument is stored in the node context. There is an api to access the NavigationArgument,. With the current implementation the ViewController classes didn't have access to the NavigationArgument. Now they can use the getNavigationArgument() from the node to get access. Also it's now possible to use the create() api to let build navigation nodes from other assemblers. In the past you must use the assemblers buildNode() method. This makes it nessecary to have the assemblers defining bundle in the dependency chain. Now the coupling is done via the extension point of an assembly. No furtehr dependency (except the knowledge of the NavigationNodes typeId) is nessecary. The attached patch is based on the current HEAD from 1.1.0m7
Created attachment 133330 [details] patch file with the enhancement patchfile is based on the latest HEAD of 1.1.0m7
hi stefan, why does the controller need to access the navigationargument itself. I thought the important part was to access the object inside the NavigationArgument which can already be accessed with the current API. Is the create() api meant to replace all your assemblers as an alternate API for building node trees ? Just curious.
fixed for 1.1.0.M7
