Add a --quiet option for fix

[alanmcruickshank]

This resolves #1834. Another oldie, but perhaps useful for some users. Added a few type hints along the way.

[coveralls]

Pull Request Test Coverage Report for Build 4720013971

• 47 of 47 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 4719563851:	0.0%
Covered Lines:	17845
Relevant Lines:	17845

---

💛 - Coveralls

[WittierDinosaur]

What's the rationale behind requiring force?

[alanmcruickshank]

What's the rationale behind requiring force?

I was thinking that unless there's some output, then you wouldn't know what you were confirming. That means that it would feel a bit strange to ask for confirmation.

If you were a user and used --quiet but not --force what would you expect to happen? I'm very happy to take a different approach on this.

@G3rtjan, as the original poster of the issue, do you have views?

[WittierDinosaur]

i was thinking it'd be along the lines of:

sqlfluff fix --quiet
12 fixable violations found
Confirm fix?

[G3rtjan]

i was thinking it'd be along the lines of:

sqlfluff fix --quiet
12 fixable violations found
Confirm fix?

Yes, this is what I would expect. It's less verbose compared to the full list of fixes, but still enables a decision (unless you combine it with --force)

[alanmcruickshank]

@WittierDinosaur - I've revised the treatment of --force. With --force you now get:

> sqlfluff fix -d ansi test1.sql --quiet -x f -f
5 fixable linting violations found
== [test1.sql] FIXED

without --force you now get:

> sqlfluff fix -d ansi test1.sql --quiet -x f
5 fixable linting violations found
Are you sure you wish to attempt to fix these? [Y/n] ...
== [test1.sql] FIXED
All Finished � �!

and with -v/--verbose you still get an error:

> sqlfluff fix -d ansi test1.sql --quiet -x f -v
ERROR: The --quiet flag can only be used if --verbose is not set.

[WittierDinosaur]

LGTM