Workiva / Workiva/dependency_validator
Validation should fail if a dependency is only used for its builder
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 66
- Forks
- 26
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 7
Description
A dependency, like built_value_generator, which provides a builder is ignored by the dependency check. As a result, you may place it in your dependency list without issue.
My expected outcome is that built_value_generator, when used for its builder, would fail validation if it was not lowered to a dev_dependency.
The following packages contain builders that are auto-applied or referenced in "build.yaml"
* built_value_generator
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 tracing the dependency check for builder-only packages, using built_value_generator and the build.yaml builder configuration described in the issue. Reproduce the case with built_value_generator as a regular dependency; done means validation reports it and accepts the configuration only when it is a dev_dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100