The new version of Flow wants us to type the navigation prop on all ReactNav screens so it can make sure we're using .Screen components correctly in navigators.
Depends on D9992
Paths
| Differential D9993 Authored by ashoat on Nov 27 2023, 12:31 AM.
Details Summary The new version of Flow wants us to type the navigation prop on all ReactNav screens so it can make sure we're using .Screen components correctly in navigators. NOTE: CI will fail on this diff. I considered the possibility of fixing Flow errors BEFORE upgrading Flow, but it wasn't possible... in some cases, the fixes to support the new version of Flow caused errors in the old version. I could have hidden these type errors with $FlowFixMe lines and then later revert those, but that seemed like too much busy work.
Depends on D9992 Test Plan Confirm the Flow errors go away
Diff Detail
Event Timelineashoat created this revision. Harbormaster completed remote builds in B24434: Diff 33637.Nov 27 2023, 12:31 AM2023-11-27 00:31:28 (UTC-8) This revision is now accepted and ready to land.Nov 27 2023, 3:41 AM2023-11-27 03:41:13 (UTC-8) Closed by commit rCOMM34f640c23850: [Flow202][native][skip-ci] [9/x] Type navigation prop on all ReactNav screens (authored by ashoat). · Explain WhyNov 27 2023, 3:27 PM2023-11-27 15:27:50 (UTC-8) This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 33637 native/apps/apps-directory.react.js
native/profile/add-keyserver.react.js
native/profile/appearance-preferences.react.js
native/profile/backup-menu.react.js
|
Does it make sense to merge these two together? Something like