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
We should instead be passing the QueryUser back and forth as the Navigation Data and allow the ToQuery and FromQuery delegates to do the work of build the route query parameters and extracting the parameters from the route path.
The current samples for the
ToQuery
andFromQuery
usages should be refactored.Currently, we are embedding the query parameters as part of the actual route in the XAML attached property:
Uno.Samples/UI/Navigation/src/Navigation/Presentation/MainPage.xaml
Lines 110 to 122 in e9ccf60
We should instead be passing the
QueryUser
back and forth as the Navigation Data and allow the ToQuery and FromQuery delegates to do the work of build the route query parameters and extracting the parameters from the route path.We should be demonstrating how to Navigate to and from these pages through XAML- and ViewModel-navigatoin
https://platform.uno/docs/articles/external/uno.extensions/doc/Learn/Navigation/HowTo-DefineRoutes.html#viewmap
related: unoplatform/uno.extensions#2672
The text was updated successfully, but these errors were encountered: