Workiva / Workiva/over_react_codemod
Feature Request: repo-level config file
Open
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 3
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Rather than pepper the code with ignore comments, I would much rather configure a set of patterns that a codemod should ignore in a file at the root of a repo, similar to how dart_dev works.
https://github.com/Workiva/dart_dev#project-level-configuration
Contributor guide
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 by reviewing how ignore comments are currently handled and the project-level configuration approach described in the linked dart_dev documentation. Define the root-level configuration format and how its patterns interact with existing ignores; done means a repository can configure codemod exclusions without peppering code with ignore comments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100