Skip to content
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

[Navigation] Avoid using reflection when accessing hardcoded regions #2151

Closed
6 tasks
nickrandolph opened this issue Jan 22, 2024 · 0 comments · Fixed by #2152
Closed
6 tasks

[Navigation] Avoid using reflection when accessing hardcoded regions #2151

nickrandolph opened this issue Jan 22, 2024 · 0 comments · Fixed by #2152
Labels
kind/enhancement New feature or request. triage/untriaged Indicates an issue requires triaging or verification.

Comments

@nickrandolph
Copy link
Contributor

What would you like to be added:

When using a TabBar or NavigationView, the associated PanelVisibilityNavigator can contain regions that are hardcoded in xaml (in contrast to a page or usercontrol that is dynamically created and added to the panel). The hardcoded regions should automatically be added as RouteMaps if they don't already exist.

Why is this needed:

In this scenario navigation should know about these regions without them being defined in a RouteMap and without using reflection to try to locate and routemap based on the path.

For which Platform:

  • iOS
  • Android
  • WebAssembly
  • WebAssembly renders for Xamarin.Forms
  • Windows
  • Build tasks

Anything else we need to know?

@nickrandolph nickrandolph added kind/enhancement New feature or request. triage/untriaged Indicates an issue requires triaging or verification. labels Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request. triage/untriaged Indicates an issue requires triaging or verification.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant