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
Is your feature request related to a problem? Please describe.
This is a request for Xamarin.Forms Shell Support.
Describe the solution you'd like
ReactiveUI to support Xamarin.Forms Shell as opposed to the current INavigation interface. This will introduce an entirely new paragadim into ReactiveUI for navigation and make the current RoutingState obsolete in Shell applications. The new Shell navigation will be specific to the Xamarin.Forms platform.
Describe alternatives you've considered
None. There is a perfectly convenient routing system in Xamarin Forms that ReactiveUI supports. But it doesn't support Shell. Currently you have to choose between Xamarin.Forms Shell or ReactiveUI Routing. The current ReactiveUI routing system will not support shell out of the box.
NOTE
There is currently some work the Xamarin.Forms team is doing to support MVVM with Shell. Last I was told that work is being tracked herexamarin/Xamarin.Forms#5166
Describe suggestions on how to achieve the feature
An abstraction over the Shell to make it less static and more in line with MVVM patterns. Not sure the specifics of what this looks like.
Additional context
The Xamarin.Forms Shell approach is a Page => Page approach. ReactiveUI has been actively trying to move to the ViewModel based navigation. These two concepts are not congruent with each other, this doesn't mean they won't work together. This simply means that we will have to work to address concerns in our approach to get the most value.
The text was updated successfully, but these errors were encountered:
Thank you for contributing to our project financially. We will handle your issue with priority support. To make sure we don't forget how special you are, we added a priority label to your issue.
Is your feature request related to a problem? Please describe.
This is a request for Xamarin.Forms Shell Support.
Describe the solution you'd like
ReactiveUI to support Xamarin.Forms Shell as opposed to the current
INavigation
interface. This will introduce an entirely new paragadim into ReactiveUI for navigation and make the currentRoutingState
obsolete in Shell applications. The newShell
navigation will be specific to the Xamarin.Forms platform.Describe alternatives you've considered
None. There is a perfectly convenient routing system in Xamarin Forms that ReactiveUI supports. But it doesn't support Shell. Currently you have to choose between Xamarin.Forms Shell or ReactiveUI Routing. The current ReactiveUI routing system will not support shell out of the box.
NOTE
There is currently some work the Xamarin.Forms team is doing to support MVVM with Shell. Last I was told that work is being tracked here xamarin/Xamarin.Forms#5166
Describe suggestions on how to achieve the feature
An abstraction over the Shell to make it less static and more in line with MVVM patterns. Not sure the specifics of what this looks like.
Additional context
The Xamarin.Forms Shell approach is a Page => Page approach. ReactiveUI has been actively trying to move to the ViewModel based navigation. These two concepts are not congruent with each other, this doesn't mean they won't work together. This simply means that we will have to work to address concerns in our approach to get the most value.
The text was updated successfully, but these errors were encountered: