With more people working on the project its finally time to following the linting guidelines. They'll help keep the style consistent throughout the project and make it easier for new people to understand the repo. The google c++ style guide has a configuration for cpplint and is included in requirements.txt. I listed everyone with a user code library that I felt was most applicable to what they are working on right now. For the library you are assigned the errors that show up in the linter will need to be fixed included corresponding example and test files. Each library should have its own branch name prefixed with fix-lint- and you can list me as a reviewer.
With more people working on the project its finally time to following the linting guidelines. They'll help keep the style consistent throughout the project and make it easier for new people to understand the repo. The google c++ style guide has a configuration for
cpplint
and is included inrequirements.txt
. I listed everyone with a user code library that I felt was most applicable to what they are working on right now. For the library you are assigned the errors that show up in the linter will need to be fixed included corresponding example and test files. Each library should have its own branch name prefixed withfix-lint-
and you can list me as a reviewer.Steps to lint
Create venv if not already created
For stm32
For esp32
Assignments
ads
- @ahmedfalah01battery
- @2004Islandfram
- @stevegtaylorphytos31
- @Kshitijpatil16sdi12
- @gxjacobssensors
- @jmadden173