Expose protoPath dependencies to consumers
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.4k
- Forks
- 627
- Avg merge
- 3d 15m
- Merged PRs (30d)
- 20
Description
Right now, consumers have to manually add protoPath dependencies their own direct dependencies depend on. It'd be sweet for Wire to expose some kind of metadata for so it'd be able to resolve them automatically without users having to manually add protoPath. Maybe the trick would be to expose protoPath dependencies of types which are not referred at all after treeshaking.
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
The issue names no files, tests, or entry points. Start by tracing how Wire handles protoPath dependencies and tree-shaking, then determine what consumer-facing metadata could expose dependencies that remain needed after unused types are removed. Done means consumers can resolve those dependencies without manually adding protoPath entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, kotlin
- Domain
- api, build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100