jraska / jraska/modules-graph-assert
Baseline for needs migration
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 640
- Forks
- 35
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
This is a feature suggestion that could help existing projects that have many violations. Instead of having big aliases such as NeedsMigration, I wonder if we could have violation baseline which we can generate (similarly to detekt/lint)
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
No implementation files, tests, or entry points are named. Start by locating how the Gradle plugin records and reports violations, then review how detekt or lint generate baselines. Done means agreeing on the baseline format, generation flow, and how existing violations are excluded without broad aliases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100