Report on (and potentially improve) flow type coverage.
Description
In learning to work with Flow, I noticed that the coding environment has some type coverage gaps. These gaps occur where we pass around or receive undocumented objects without describing their deeper structure using Flow type annotations. This ticket covers reporting on type coverage (perhaps by logging warnings when running npx flow check).
We could also choose to close some of the gaps as part of this issue, for example by:
Installing additional flow-typed definitions for the packages we use.
In learning to work with Flow, I noticed that the coding environment has some type coverage gaps. These gaps occur where we pass around or receive undocumented objects without describing their deeper structure using Flow type annotations. This ticket covers reporting on type coverage (perhaps by logging warnings when running npx flow check).
We could also choose to close some of the gaps as part of this issue, for example by:
Installing additional flow-typed definitions for the packages we use.
Adding a configuration option to let us opt a particular line out of coverage reporting.
Adding type annotations as required.