Closed krisgesling closed 3 years ago
I don't like using util
as the package name for the abstracted code. To me, util
implies functionality that has nothing to do with business logic. Examples include logging, file/directory handling, wrappers around third party tools, etc. I would like to see this directory named either skill
or lib
or source
. I also want to see the public API into this package defined in __init__.py
. I want this to become a common practice at Mycroft.
For the tests, we already have a test directory for the behave tests. Unit tests should be included there. I don't like having two places for test code.
We need to stop using one letter variable names too.
k ;)
Description
In preparation for bug fixes, this is a clean up of the code base with no functional changes.
So far:
To do:
Type of PR
Testing
Integration tests pass Everything continues to work as previously.
To run unit tests: