Replace /* @flow */ with entry in .flowconfig

When introducing Flow to legacy code, it's nice to specify on a per-file basis what files Flow should analyze. Thus, we have the `/* @flow */` or `/* @flow weak */` comments at the top of each file. Once Flow is widely used in a project, I imagine that this would become extremely tedious. Or worse, someone may accidentally fail to include the comment and then we'll have no protection on that file with no warning that we don't. I suppose `flow check --all` exists for these cases, but that's an extremely inflexible solution. Couldn't all these cases (analyze a few files, most files, or all files from a project) be solved more simply by providing a way to specify a glob or regex in .flowconfig that determines what files to analyze? That's what I assumed the `[include]` option was for, but it looks like it still requires the files listed to include the `/* @flow */` comment (so it's more for checking files in a folder outside the one where .flowconfig is located).

Posted by cletusw on Feb 25, 2015, 6:57 PM

Tags

• reliability (Other)

Related issues

• This is my biggest problem with agents, they constantly defensively code for cases that have no chance of happening and in most cases a p...
• I wish there was something like LEAN for biology.
• The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
• I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
• I hate that I'm in deep enough to know what you mean.
• The biggest problem with “AI” is that big corps are shoving it down our throats.