Code Compliance output grouping
Open
Nobody has claimed this yet.
area: buildsystem
improvement
just do it
lang: python
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
The output of the code compliance should be grouped by the file that is tested - makes it a lot easier to fix all the issues in a file, without having to jump around a lot.
The code compliance checks are performed in openage/buildsystem/codecompliance.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in openage/buildsystem/codecompliance and trace how compliance results are collected and rendered. Check the current output path and determine how tested files are represented; done means all reported issues are grouped under the file they belong to, making per-file fixes easier to follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100