swiftlang / swiftlang/swift-java
Move Foundation support into a common package
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 1.2k
- Forks
- 123
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 16
Description
Currently, Foundation.Date support is generated locally within each package.
This creates duplicate classes like com.packageA.Date and com.packageB.Date when multiple Swift packages use swift-java, which is confusing on the Java side.
Moving Foundation support into SwiftJava (along with SwiftKitCore and SwiftKitFFM) would solve this problem.
The implementation is small, so I think this will have minimal impact.
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
Inspect how Foundation.Date support is generated within each package, then compare the SwiftJava, SwiftKitCore, and SwiftKitFFM packages as possible common locations. Done means multiple Swift packages using swift-java no longer generate duplicate Java Date classes such as com.packageA.Date and com.packageB.Date.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, swift
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100