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 have installed fta-cli@1.0.0 on my MacBook. I want to run static analysis on code in a project, but not on any tests, documentation or Storybook stories, etc. that are placed near source code.
Here is my fta.json file that is completely ignored by fta running from npm script in package.json, npm run --config-path="./fta.json":
My fta.json is located in the root of the project and according to documentation it should be picked up automatically, but it does not. Specifying --config-path does not help. I want to ignore any .spec, .docs or. stories, or .types files included in src but this is the output I get:
I tried changing other configuration in the file, like output_limit but they get ignored, too.
The text was updated successfully, but these errors were encountered:
Hi @zettadam thanks for reporting. This might be due to some quirkiness of how the exclude/extensions options work.
Do you still have the problem if you clear out extensions? It seems like something is overriding your exclusions. You could also try values like *.spec.jsx (including the asterisks) to see if it changes the result.
Hi,
I have installed
fta-cli@1.0.0
on my MacBook. I want to run static analysis on code in a project, but not on any tests, documentation or Storybook stories, etc. that are placed near source code.Here is my
fta.json
file that is completely ignored byfta
running from npm script in package.json,npm run --config-path="./fta.json"
:My
fta.json
is located in the root of the project and according to documentation it should be picked up automatically, but it does not. Specifying--config-path
does not help. I want to ignore any.spec
,.docs
or. stories
, or.types
files included insrc
but this is the output I get:I tried changing other configuration in the file, like
output_limit
but they get ignored, too.The text was updated successfully, but these errors were encountered: