moved logic from cli to loader to clean up interface when used as a p…

[chrisantonellis]

moved configuration loading logic out of CLI module to isolate concerns, and to clean up interface when little-cheesemonger is used as a python package instead of a CLI

fixed associated tests and wrote some more

90% coverage enforcement has been disabled to allow integration tests to pass until a clean workaround is found (suggestions welcome)

[codecov]

Codecov Report

Merging #17 (b74fd9f) into main (824e3e6) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #17   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            7         7           
  Lines          188       189    +1     
  Branches        16        16           
=========================================
+ Hits           188       189    +1     

Impacted Files	Coverage Δ
little_cheesemonger/_cli.py	100.00% <100.00%> (ø)
little_cheesemonger/_loader.py	100.00% <100.00%> (ø)
little_cheesemonger/_run.py	100.00% <100.00%> (ø)

[jamescurtin]

90% coverage enforcement has been disabled to allow integration tests to pass until a clean workaround is found (suggestions welcome)

This only affects running integration tests locally, as codecov automatically combines all coverage reports and evaluates the combined coverage against the minimum defined in .github/codecov.yml, right?

Two possible options I see for maintaining minimum coverage when running local integration tests (first would be the easiest, I think):

1. Create a .coveragerc-integration config file (or something like that) and add the --cov-config argument to pytest when running the integration tests. This would allow you to have different minimum levels of coverage for unit and integration tests.
2. If you can run the unit tests in the same container as the integration tests, you could use coverage combine (or the --cov-append argument in pytest-cov) to generate a combined coverage report that is evaluated at the end.

[plannigan]

I think this line should be moved back to the _cli.py. When being used as a library, it should be the caller's responsibility to configure logging outputs. This would make run() only concerned with out little_cheesemonger loggers operate.

[plannigan]

You could use a different configuration file for the integration test. That would allow you to have a different required value.