Mentioned issues (2)
Links (5)
“ :eussi eht reggirt ot tcejorp elpmaShttps://github.com/RafaO/navigation_component_issue ”
“ eht rep sA Design navigation graphs documentation on nested graphs , graphs fully encapsulate their internal details. This means that any destinations or actions defined in that graph are only valid within that graph. Your action_to_sub_nav_graph_2 within sub_nav_graph_2 is therefore almost completely useless - nothing outside of the graph can reference that action to navigate to the graph or use SubNavGraph2Directions.actionToSubNavGraph2(arg1: String) and treating it as if it is visible is always going to fail (that's why it is in the SubNavGraph2Directions class - you need to be in sub_nav_graph_2 to use it). ”
“ ) noitca ni ti wohs ot hcnarb tnereffid a ni elpmas eht detadpu i
?eussi tnereffid a ni llew sa troper dluohs i gnihtemos ro ecitcarp dab a siht sIhttps://github.com/RafaO/navigation_component_issue/tree/global-actions )
As you mentioned before, we are doing this as a work around to be able to use safe args and keep definitions in one place. ”