skiptools / skiptools/skip-bridge
Customize handling of un-bridgable types/methods
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 6
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
When a public type or method cannot be bridged from Swift to Kotlin, the skipstone plugin will fail with an error. For packages that might have a large portion of public API that isn't expected it be bridgable, it can be cumbersome to annotate these all with // SKIP @nobridge.
We could have a skip.yml option called unbridgable that accepts fail (the default), warn, and ignore. The latter two would avoid attempting to create a bridge to a type or method that isn't bridgeable.
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 locating how the skip.yml configuration is parsed and where the plugin reports unbridgeable public types or methods. Trace the existing failure path, then verify that fail remains the default and that warn and ignore avoid bridge generation as described; add or run the relevant plugin tests if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, swift
- Domain
- mobile-dev, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100