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
I want to have a reusable viewmodel that can emit results back to the calling viewmodel.
If we can get something like a NavigateForResult with a generic type then that would be neat. Interactions are great but I believe they are best for very simple dialogs and simple results. What about a complex object? What if it's prompted as a popup, but as a full page? Yes we can subscribe to events from the ViewModel before passing it through to Navigate.Execute() but that just returns a IRoutableViewModel object and will make the pipeline less neat :D
ChooseContacts= ReactiveCommand.CreateFromObservable(()=> HostScreen.Router.NavigateForResult.Execute(new ContactsResultViewModel()).Select(contacts =>/* transform result */));
We can do it by making a generic IRoutableViewModel<TResult> so the routing commands can listen to it's result.
The text was updated successfully, but these errors were encountered:
I want to have a reusable viewmodel that can emit results back to the calling viewmodel.
If we can get something like a
NavigateForResult
with a generic type then that would be neat. Interactions are great but I believe they are best for very simple dialogs and simple results. What about a complex object? What if it's prompted as a popup, but as a full page? Yes we can subscribe to events from the ViewModel before passing it through toNavigate.Execute()
but that just returns aIRoutableViewModel
object and will make the pipeline less neat :DWe can do it by making a generic
IRoutableViewModel<TResult>
so the routing commands can listen to it's result.The text was updated successfully, but these errors were encountered: