C2LC-577: Make $FlowFixMe exclusions more specific.

Metadata

Source
C2LC-577
Type
Bug
Priority
N/A
Status
To Do
Resolution
N/A
Assignee
N/A
Reporter
Tony Atkins [RtF]
Created
2022-01-05T09:57:10.897-0500
Updated
2022-09-21T11:42:27.200-0400
Versions
N/A
Fixed Versions
N/A
Component
  1. Coding Environment

Description

When researching C2LC-576, I tried looking at the flow check output with warnings:

npx flow check --include-warnings

This revealed warnings about most of our $FlowFixMe usages. We should, but are not specifying which errors to ignore, as in this example:

{
      "kind":"infer",
      "level":"warning",
      "suppressions":[],
      "message":[
        {
          "context":"        // $FlowFixMe event target doesn't know value",
          "descr":"Suppression is missing a code. Please update this suppression to use an error code: `$FlowFixMe[prop-missing]`",
          "type":"Blame",
          "loc":{
            "source":"/Users/duhrer/Source/rtf/c2lc-coding-environment/src/WorldSelector.js",
            "type":"SourceFile",
            "start":{"line":65,"column":9,"offset":1917},
            "end":{"line":65,"column":53,"offset":1962}
          },
          "path":"/Users/duhrer/Source/rtf/c2lc-coding-environment/src/WorldSelector.js",
          "line":65,
          "endline":65,
          "start":9,
          "end":53
        }
      ],
      "error_codes":[]
    }

This ticket covers resolving these warnings.