[v2] Coding Guidelines
The following document proposes the guidelines to be followed for the implementation beat.editor version 2.
- all features need mandatory tests to be validated
- code should be well written and documented to be validated
- usage of black for python and other tools to standardize the code
- we will be updating a set of guidelines to follow for the new version
- 1 merge request per feature and bug fix only
- only atomic commits
- clean commit messages (i.e.: [plotter] added plotter lines generation. Fixes #xx)
- A nose testable editor or we could look at pytest-qt too