Command line option: quiet

[z4f1r0v]

Introduce quiet parameter in Settings
Don't write to console if the quite is added to cmd args
Make tests happy
Set CliTestRunner.scala to quite logs

[coveralls]

Coverage decreased (-0.6%) to 67.368% when pulling cc6d25e on alexanderzafirov:master into e3b1d40 on hrj:master.

[z4f1r0v]

Hello @hrj! This is a stab at #111
I decided to go with an extra parameter to Settings since this is a setting to the app. I don't like the way this parameter "spills" in all the tests and is actually only used in the App.scala. Nevertheless I decided that this needs to be addressed in a separate PR.
If you are happy with this maybe we can have a discussion about the architecture of the app. I see some concepts could be refined. IntelliJ also suggests some modifications to the code - mostly cosmetics, I guess - that can also be applied if you agree.

[hrj]

Hey @alexanderzafirov !

Firstly, sorry, there's been a slight misunderstanding. The quiet parameter is supposed to suppress "log" output, such as "Processing file xyz.ledger" or "Writing to pqr.xml". The actual reports should not be suppressed.

Secondly, you need to create a new branch and rebase these changes on top of upstream master.

Something along these lines:

#create new branch
git checkout -b i111-quiet

# add this repository if not already done
git remote add hrj git@github.com:hrj/abandon.git

# get all the latest changes from this repo
git fetch hrj

# merge the latest
git merge hrj/master

# rebase
git rebase hrj/master

# push to your fork
git push origin i111-quiet

After this you can create a new pull-request from your branch i111-quiet to the master branch here. If you are comfortable with git, you could update this PR in place, but to keep things simple I will close this PR.

About architecture, sure! You can create a new issue for it and we can discuss there.

cheers!