The new version of Flow is pushing us to specify all of these type params. Presumably Flow was always unable to infer them, but the new version is stricter about forcing type params when they can't be inferred.
Depends on D9993
Paths
| Differential D9994 Authored by ashoat on Nov 27 2023, 12:32 AM.
Details Summary The new version of Flow is pushing us to specify all of these type params. Presumably Flow was always unable to infer them, but the new version is stricter about forcing type params when they can't be inferred. 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 D9993 Test Plan Confirm the Flow errors go away
Diff Detail
Event Timelineashoat created this revision. Harbormaster completed remote builds in B24435: Diff 33638.Nov 27 2023, 12:32 AM2023-11-27 00:32:11 (UTC-8) This revision is now accepted and ready to land.Nov 27 2023, 3:42 AM2023-11-27 03:42:48 (UTC-8) Closed by commit rCOMM3e94e3017d50: [Flow202][native][skip-ci] [10/x] Add type params to ReactNav… (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 33638 native/chat/chat.react.js
native/navigation/overlay-navigator.react.js
native/navigation/root-navigator.react.js
native/navigation/tab-navigator.react.js
|
For other tooltip actions we don't need to manually set this style. Can we use the mechanism we already have, or are there any reasons for not doing so?