feat: Add a -r/--reporters configuration flag

[JoseAngel1196]

This PR

Fixes #50

[codecov]

Codecov Report

Merging #89 (9037176) into main (43cade8) will decrease coverage by 0.29%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##             main      #89      +/-   ##
==========================================
- Coverage   74.85%   74.57%   -0.29%     
==========================================
  Files          15       15              
  Lines         704      704              
==========================================
- Hits          527      525       -2     
- Misses        168      170       +2     
  Partials        9        9              

Flag	Coverage Δ
unittests	74.57% <20.00%> (-0.29%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
cmd/root.go	30.00% <100.00%> (-4.38%)	⬇️
config/config.go	74.19% <ø> (ø)
internal/scan.go	0.00% <0.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[tarkatronic]

I'm going to set this as hacktoberfest-accepted since I think the core direction is right. Unfortunately my recent PR #88 broke CLI flags, which will need to be fixed separate of this.

One good additional test here might be to ensure that setting reporters = ["foo"] in a config file makes it through to the config object. Or you could even just add that on to an existing test.

The one other change is that we need to be sure the console reporter is only used if it is activated!

[JoseAngel1196]

I'm going to set this as hacktoberfest-accepted since I think the core direction is right. Unfortunately my recent PR #88 broke CLI flags, which will need to be fixed separate of this.

One good additional test here might be to ensure that setting reporters = ["foo"] in a config file makes it through to the config object. Or you could even just add that on to an existing test.

The one other change is that we need to be sure the console reporter is only used if it is activated!

Done! I considered re-using the existing TestGetUserConfigFromEnv instead of adding a new test.

[tarkatronic]

Love this, thank you!