JakeWharton / JakeWharton/kmp-missing-targets
Handle deprecated targets
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 145
- Forks
- 1
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 10
Description
`wasm`, `androidNativeArm32Hfp`, `zephyr`(wtf?!?), `js` (non-IR)
These need to not fail the build, but still be shown with some kind of indicator (strike though?)
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 locating where the plugin evaluates or displays the `wasm`, `androidNativeArm32Hfp`, `zephyr`, and non-IR `js` targets. Check how unsupported targets currently affect the build, then define the indicator behavior for deprecated targets and verify that they no longer fail the build while remaining visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript, kotlin, wasm
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100