By week 1 I finally got a part of the hardest thing regarding this project: a way of maintaining the requirements for the bears easily.
To help myself with that, I created a PackageRequirement class. Now each bear can have a REQUIREMENTS tuple made of instances of the PackageRequirement class.
To automatize working, I worked on two separate things:
- creating a “multiple“ method, which helps you instantiate multiple instances of that class instead of calling out the same class again all over and over again
- creating subclasses, such as PythonRequirement and NPMRequirement, which have the manager already set to “pip“, respectively “npm“.
These classes receive 3 arguments: manager, package name and version.
However, there’s more: you can also avoid specifying the version, and this way, the latest will automatically be specified.
On the other hand, I am working on a bearUploader tool. This will upload a MockBear (which I chose to be cpplintbear for the basic functionality it provides) to provide continuous integration. This is still work in progress, as the tool only creates a setup.py file for the bear right now, but it’s going to be done the next week.
So for the next week: More on the bearUploader tool!