You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CharactersListFragment.kt
...
is CharactersListViewEvent.OpenCharacterDetail ->
findNavController().navigate(
CharactersListFragmentDirections
.actionCharactersListFragmentToCharacterDetailFragment(viewEvent.id))
It's not good decision without scalable points for projects "under Forma". And we think that will be good have some abstraction navigation layer, which will protect project structure, architecture from navigation tools dependencies, especially codegen from Navigation component.
That's why need to create own navigation system, which will be use by app presentation layer. May be after, we will think about additional navigation targets for Forma.
See here, some mind ideas how it may be look
The text was updated successfully, but these errors were encountered:
It's better to BackTo have field Class<Destination> instead of Destination. In that case you have no need to create such Destination with it's explicit params when you just want to go back.
Our sample uses Jetpack Navigation. It brought some strong dependencies through whole project, such as
or codegen into
It's not good decision without scalable points for projects "under Forma". And we think that will be good have some abstraction navigation layer, which will protect project structure, architecture from navigation tools dependencies, especially codegen from Navigation component.
That's why need to create own navigation system, which will be use by app presentation layer. May be after, we will think about additional navigation targets for Forma.
See here, some mind ideas how it may be look
The text was updated successfully, but these errors were encountered: