sonarqubesonarjs

SonarJS marks issues if FlowType type annotations from the standard library are present

SonarJS 4.0 ignored FlowType annotations, but with SonarJS 4.1 they are marked as reference error (Rule: javascript:S3827).

I just want to clearify if this is intended behaviour and what is the intended "workflow" regarding this.

if it is not a bug, do i need to add all those References to the globals, or what is the best practice to handle this behaviour?

enter image description here

Thank you

Solution

  • This is intended behavior, SonarJS version 4.1 now treats Flow Types as symbols, and core flow types are automatically resolved because they are available in the new flow environment. Types should be resolved automatically when they are correctly imported with import type syntax.

    An issue was created to include React Flow Types in globals by default.