wpilibsuite / wpilibsuite/native-utils
Easier way to resolve an entire native dependency set
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5
- Forks
- 30
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 4
Description
https://github.com/GrappleRobotics/libgrapplefrc/blob/master/build.gradle#L112
The way these are being grabbed here is kind of hacky, we should have a better way to support this.
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
Start by reading build.gradle around line 112 in the linked libgrapplefrc repository to understand how the native dependency set is currently resolved. The issue does not specify the replacement approach or acceptance criteria, so clarify the desired API and what would count as removing the hack before estimating or implementing the work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100