-
Pre-commit is running a few standard checks, further improvement could be gained from:
- pylint
- [x] code
- [x] tests
- remaining problems are ignorable
- [x] (not sure if this needs…
-
- [ ] Create components to handle some part of the pages
- [x] Caching must be supported everywhere it's necessary
- [ ] Make it DRY #10
- [ ] Treat error cases
- [ ] Look for a better way to impl…
-
Hi! I am creating an issue because even though the project seems quite interesting, the code quality (from what I saw) is at best okay-ish, at worst simply bad, be it from only PEP8 weirdness, or non-…
-
- [ ] Improving readability and quality.
- [ ] Refactoring code.
- [ ] Create readme
- [ ] Code documentation
-
It would be nice to get a view of the code quality for a repo overall or per file. Right now, the only way to see this is by mousing over the code itself to see the quality score.
Many VS Code ext…
-
-
Ideas:
- Set up automation of tests and code quality checks
- Add docstrings
- Improve formatting (yapf)
- Fix typing (mypy)
- Work in linter advice (pylint)
- Run spell checker
-
With the increased functionality from #2 the file is getting pretty big and hard to navigate - need to strip it down into smaller more modular chunks. Especially extracting out HTTP server
-
Currently there are a lot of warnings when compiling OpenBoard. In order to increase code quality we should aim to have no warnings even with `-Wpedantic` switched on.
I have seen in other projects…
-
- from an audit tag: /// @audit is this precise, have there been instances where the aave rate is negative?
- from an audit tag: // @audit - move docs to IRateOracle. Add additional parameter to use …