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
I would like support for selectively enabling lint rules at a per-directory (or glob) level.
We have a large codebase at Stripe that did not start with the strictest lint rules. What we would like to do is enable new lint rules in specific directories, so that new code written in those directories can be safer. Over time, we can migrate other directories to accept new lint rules.
This can either be implemented with an extension to .flowconfig, or perhaps allowing per-directory .flowconfig files that can inherit from parent directory .flowconfig files. I don't have strong opinions for a solution, but would love to see this problem solved.
Use case
See above.
The text was updated successfully, but these errors were encountered:
For anyone not aware, you can get part of the way there with @flow strict annotations on files you want to be checked against a stricter set of rules (configurable in .flowconfig which lint rules those are):
Proposal
I would like support for selectively enabling lint rules at a per-directory (or glob) level.
We have a large codebase at Stripe that did not start with the strictest lint rules. What we would like to do is enable new lint rules in specific directories, so that new code written in those directories can be safer. Over time, we can migrate other directories to accept new lint rules.
This can either be implemented with an extension to
.flowconfig
, or perhaps allowing per-directory.flowconfig
files that can inherit from parent directory.flowconfig
files. I don't have strong opinions for a solution, but would love to see this problem solved.Use case
See above.
The text was updated successfully, but these errors were encountered: