Workiva / Workiva/dependency_validator
Validation rule to prevent `any` version
Open
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 66
- Forks
- 26
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 7
Description
pubspec.yaml files technically support any as a possible version:
some_dep: any
some_dep2:
some_dep3:
hosted:
name: some_dep3
url: https://some_url.org
While this is valid for development use cases, this will fail during publish to pub, and would be nice if dependency_validator could catch
Consider this as an opt-in functionality
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 how dependency_validator reads pubspec.yaml dependency declarations and how opt-in validation rules are configured. Cover the shown scalar, empty, and hosted dependency forms, and make completion mean that enabled validation reports any versions while leaving the default behavior unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100