Page MenuHomePhabricator

[Flow202][native][skip-ci] [58/x] Destructure this.lastMessageSent before checking its value
ClosedPublic

Authored by ashoat on Nov 27 2023, 1:30 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, May 5, 12:33 PM
Unknown Object (File)
Mar 5 2024, 7:19 AM
Unknown Object (File)
Mar 5 2024, 7:19 AM
Unknown Object (File)
Mar 5 2024, 7:19 AM
Unknown Object (File)
Mar 5 2024, 7:19 AM
Unknown Object (File)
Dec 13 2023, 2:17 AM
Unknown Object (File)
Dec 12 2023, 8:09 PM
Unknown Object (File)
Dec 9 2023, 4:31 AM
Subscribers
None

Details

Summary

The new version of Flow appears to be worried that the value of this.lastMessageSent will change after it's checked. The error goes away if I assign the value to a local variable before checking it.

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 D10041

Test Plan

Confirm the Flow errors go away

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable