Page MenuHomePhabricator

[Flow202][native][skip-ci] [5/x] Fix parameterization of ReactNav getParent
ClosedPublic

Authored by ashoat on Nov 27 2023, 12:27 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, May 12, 2:18 PM
Unknown Object (File)
Tue, May 7, 1:08 AM
Unknown Object (File)
Tue, May 7, 1:08 AM
Unknown Object (File)
Tue, May 7, 1:07 AM
Unknown Object (File)
Tue, May 7, 12:54 AM
Unknown Object (File)
Fri, May 3, 4:11 PM
Unknown Object (File)
Wed, May 1, 3:42 PM
Unknown Object (File)
Wed, May 1, 8:50 AM
Subscribers
None

Details

Summary

Flow was having a hard time realizing that ChatNavigationProp (definition) and TabNavigationProp (definition) are valid NavigationProps (definition, relevant line).

This diff allows us to convince Flow by providing all type params of NavigationProp at the getParent invocation.

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 D9988

Test Plan

Confirm the Flow errors go away

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable