skiptools / skiptools/skipstone
Factor out SkipDrive
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 106
- Forks
- 20
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 9
Description
skipstone depends on https://github.com/skiptools/skip/tree/main/Sources/SkipDrive in a bizarre way, by symlinking SkipDriveExternal to ../../skip/Sources/SkipDrive
Instead, there should be a skip-drive library containing the SkipDrive code; skip and skipstone should depend on it.
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 comparing Sources/SkipDriveExternal in skipstone with Sources/SkipDrive in the skip repository, then trace how skipstone currently obtains that directory through the symlink. Review the package dependency declarations for both skip and skipstone. Done means SkipDrive is provided by a standalone skip-drive library and both projects depend on it without the symlink.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100