"Not yet available" errors refuse to go away, even when skip is disabled
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3.2k
- Forks
- 106
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
In https://github.com/dfabulich/skip-none-repro/tree/not-yet-available I added a reference to a Skip API that's not available, and disabled Skip completely with SKIP_ACTION = none and SKIP_ZERO = 1.
https://github.com/dfabulich/skip-none-repro/commit/cc22867904aa3a6d7ba7a88819b368bd45940870
To repro: Checkout the not-yet-available branch, "Clean Build Folder," and run the build.
Actual: "This API is not yet available in Skip. Consider placing it within a #if !SKIP block. You can file an issue against the owning library at https://github.com/skiptools, or see the library README for information on adding support"
Expected: Skip is fully disabled; this error shouldn't appear.
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
Check out the not-yet-available branch at commit cc22867904aa3a6d7ba7a88819b368bd45940870, set SKIP_ACTION = none and SKIP_ZERO = 1, clean the build folder, and run the build. Trace why the unavailable-API diagnostic remains when Skip is disabled; done means the build no longer emits that error under these settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100