Test coverage for the backend

[mustyoshi]

I need to add tests for the parsing system.

Branch

• Add type hints to all functions
• Add docstrings to all functions
• Add tests for all parsing related functions
• Add tests for all transform functions

[twjaymes]

Hello! I cloned this repo like a year ago and have been chipping away at understanding how it works. I'm fairly new to the web development side of things, but I have a background in technology. Anyway, I've had some more time recently, and have a couple questions/contributions.

There are some small things like adding dependencies (pip setuptools to the Dockerfile and html.lxml and re to billparser.importers.releases) that I needed to get it working locally on my Apple M1 MacBook Air. I've also started to write documentation and tests to help me understand how things work, maybe they would be useful. Should I submit a single pull request or go file by file? (I can use git, but I'm not 100% sure how team-development works).

[mustyoshi]

@twjaymes Hey, glad to hear you've been checking it out.
If it's just documentation and tests, one big PR would be fine, but for functional changes, smaller PRs would be better.

[twjaymes]

Okay, I've only just started the documentation, but I'd like to use an llm tool like this https://github.com/Ionio-io/LLM-agent-for-code-reviews. I'll try to do a pr next week.