Proper replacement for introspectNavigationController #386
Answered
by
davdroman
AndreiBehel
asked this question in
Q&A
|
I'am working on rafactoring of the module and updated to swiftui-introspect 1.1.1 from 0.1.1. What is proper migration for introspectNavigationController in a such case: |
Answered by
davdroman
Nov 16, 2023
Replies: 2 comments 2 replies
|
Also note, storing it in |
0 replies
|
@davdroman I saw this, but unfortunately it not working in my case( I've refactored this part as follows: And breakpoin shows that it's not called. So navigationController is nil and that is way it brokes part of the app's functionality. Maybe I've missed something? |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your navigation view inside
content? If not, then your view is inside the navigation view instead. If that's the case, then you need to override the lookup scope to introspect outwardly to find ancestors like this: