You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
If your .flowconfig file has strip_root=true in the [options] section, then linter-flow will only show squiggly lines under errors if the file has any unsaved changes.
(I'm not really clear what that setting is good for. Doesn't seem to make any difference in the output of manually running flow. Just found someone had turned it on in a project and I was confused as to why linter-flow was acting weird.)
The text was updated successfully, but these errors were encountered:
The bug still exists in v5.5.0. Adding strip_root=true to the [options] of a fresh or existing project reliably triggers it for me. Does it not for anyone else? I've attached a video in case I didn't describe it right: bug.zip. flow and flow status don't have their output affected by the option.
$ flow
test.js:3
3: var x = y;
^ identifier `y`. Could not resolve name
Found 1 error
After adding the option
$ flow
test.js:3
3: var x = y;
^ identifier `y`. Could not resolve name
Found 1 error
$ flow status
test.js:3
3: var x = y;
^ identifier `y`. Could not resolve name
Found 1 error
If your .flowconfig file has
strip_root=true
in the [options] section, then linter-flow will only show squiggly lines under errors if the file has any unsaved changes.(I'm not really clear what that setting is good for. Doesn't seem to make any difference in the output of manually running
flow
. Just found someone had turned it on in a project and I was confused as to why linter-flow was acting weird.)The text was updated successfully, but these errors were encountered: