[Custom Issue]: post Processing Code Maintenance
- Dominant language
- C++
- Stars
- 6
- Forks
- 11
- Avg merge
- 18h 7m
- Merged PRs (30d)
- 1
Description
### Contact Details
_No response_
### Are there any linked Issues or Pull Requests?
_No response_
### Brief description
Maintenance of the new post processing python module would benefit from targeted code linting, e.g. pylint, run in the CI pipeline.
i have not done this within #223 as this would make the changes hard to distinguish
hence this follow up issue:
Scope:
* establish linting in CI
* fix source to pass linting
### Further details of the issue.
_No response_
Contributor guide
Research direction
Locate the new post-processing Python module and the repository's CI configuration first. Establish a linting step in CI, then use its findings to guide the source cleanup. Done means the linting job runs in CI and the post-processing source passes it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100