adding verbose flag

[gulien]

Adds -v--verbose flag which displays less logs than the -d --debug flag.

Example when running a task:

INFO[0000] running task fmt: Runs go fmt ./...
INFO[0000] executing command [/bin/zsh -c go fmt ./...]

Feature request from #29

[gulien]

@j-vizcaino @octplane seems ok for you?

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@aa00579). Click here to learn what that means.
The diff coverage is 75%.

@@            Coverage Diff            @@
##             master      #30   +/-   ##
=========================================
  Coverage          ?   92.51%           
=========================================
  Files             ?        7           
  Lines             ?      227           
  Branches          ?        0           
=========================================
  Hits              ?      210           
  Misses            ?        9           
  Partials          ?        8

Impacted Files	Coverage Δ
app/runner/runner.go	94.91% <100%> (ø)
app/generator/generator.go	90% <100%> (ø)
app/generator/funcmap.go	66.66% <33.33%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update aa00579...2cedf5f. Read the comment docs.

[j-vizcaino]

Thanks for patching this!

Regarding option, should the tool want to stick with existing conventions, this should either be:

• keep debug and use verbose
• have a single option to set the loglevel: l/loglevel <lvl> (and merge the debug option to use this)

[j-vizcaino]

I feel this would be more conventional to name this verbose instead of info 🤔
Running orbit run --verbose would feel a bit more explicit than orbit run --info

[j-vizcaino]

Same here, maybe v/verbose instead of i/info?
Usually, i is used for input, that may be confusing to users.

[gulien]

Thank you for the feedback :)

I didn't know that verbose is some kind of a convention. For me, verbose = debug.
However, I think it's better than having a single option to set the logs level, as I don't use a lot of them (in fact, only INFO, DEBUG and ERROR - the last one being particular also, as I don't show all error logs unless we are in debug mode).