New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[VDG] UI Decoupling #8 #10239
[VDG] UI Decoupling #8 #10239
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some tests are failing due to the clipboard is null. Please fix it.
Done. Please check now. |
NavigationState.Instance
singleton.NavigationState
now implementsINavigate
MainViewModel
code that handles changes toNavigationState
and encapsulates that code inNavigationState
itself.RoutableViewModel.SetActive()
method and moves logic toNavigationState.OnCurrentPageChanged()
NavigationState.Instance
byUIContext.Navigation()
UIContext
whereUIContext.Default
would yield a new instance every time it's calledThis PR is in a workable state. Yet, as per VDG agreement this should not be merged before the release.
@SuperJMN you can rebase your PRs for ViewModel refactors off of this one.
Next step of UI Decoupling series: introduce source-generated fluent navigation APIs. Will be addressed in a future PR.