Page MenuHomePhabricator

[Flow202][lib][skip-ci] [14/23] Fix Flow issues with types of variables that get mutated
ClosedPublic

Authored by ashoat on Nov 4 2023, 12:03 PM.
Tags
None
Referenced Files
F2070713: D9706.id33292.diff
Fri, Jun 21, 10:27 PM
F2068869: D9706.diff
Fri, Jun 21, 5:57 PM
F2068761: D9706.id33553.diff
Fri, Jun 21, 5:38 PM
Unknown Object (File)
Thu, Jun 20, 11:01 PM
Unknown Object (File)
Thu, Jun 20, 6:12 PM
Unknown Object (File)
Thu, Jun 20, 8:42 AM
Unknown Object (File)
Thu, Jun 20, 4:06 AM
Unknown Object (File)
Wed, Jun 12, 5:18 PM
Subscribers

Details

Summary

There are two main categories of changes here, and both pertain to variables getting mutated:

  1. let declarations where the variable is reassigned later
  2. const declarations of mutable collections that are mutated later

In both of these cases, Flow now wants us to annotate the declaration to cover both the type of the data that's initialized, and also the mutations that later occur.

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 D9705

Test Plan

Confirm the Flow errors go away

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Nov 4 2023, 12:28 PM
Harbormaster failed remote builds in B23748: Diff 32710!
This revision is now accepted and ready to land.Nov 5 2023, 11:03 AM

Lint fixes for last rebase

ashoat retitled this revision from [Flow202][lib] [14/23] Fix Flow issues with types of variables that get mutated to [Flow202][lib][skip-ci] [14/23] Fix Flow issues with types of variables that get mutated.Nov 19 2023, 11:48 AM