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
Flow files frequently have // @flow annotations at the top of them. From my testing, telling quick-lint that flow files are typescript(react) doesn't add any false positives.
While not perfect, it's better than nothing.
Request: When quick-lint sees a @flow annotation, treat it as TypeScript
The text was updated successfully, but these errors were encountered:
Flow files should be treated as Flow, not TypeScript. There are important differences in syntax.
I do not plan on implementing Flow parsing support in quick-lint-js any time soon. However, quick-lint-js should probably detect @flow and not parse the file in this case. Would that be a good enough solution for you?
Flow files frequently have
// @flow
annotations at the top of them. From my testing, telling quick-lint that flow files are typescript(react) doesn't add any false positives.While not perfect, it's better than nothing.
Request: When
quick-lint
sees a@flow
annotation, treat it as TypeScriptThe text was updated successfully, but these errors were encountered: