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
Copy file name to clipboardExpand all lines: versioned_docs/version-8.x/upgrading-from-7.x.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,9 @@ In React Navigation 8, we reworked the types to automatically determine the corr
87
87
+ const navigation = useNavigation('Profile');
88
88
```
89
89
90
-
If you're using dynamic configuration, unfortunately we cannot currently infer the types automatically. So it still requires manual annotation. However, now you need to use `as` instead of generics to make it clearer that this is unsafe:
90
+
If you're using dynamic configuration, there is limited support for automatic inference of types. The available screens, params etc. can be inferred, so actions such as `navigation.setParams`, `navigation.navigate` etc. will be properly typed. However, navigator specific types such as `push`, `setOptions`, `addListener` etc. cannot be inferred. So it still requires manual annotation for those cases.
91
+
92
+
Additionally, now you need to use `as` instead of generics to make it clearer that this is unsafe:
0 commit comments