swiftlang / swiftlang/swift-android-examples
Unify Gradle build styles
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 568
- Forks
- 40
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 2
Description
In some places, the examples use the modern (and preferred) build.gradle.kts kotlinscript syntax, and in others they use the older build.gradle groovy syntax (like in swift-java-weather-app/weather-lib/build.gradle and hello-swift-java/hashing-lib/build.gradle).
It would be good to standardize on a single style for the sample build scripts, not least because it would enable us to share some of the logic with the root swift-android.gradle.kts.
This could also serve as a playground for an eventual set of official recommendations for how to construct Gradle projects that use Swift without necessarily relying on any external plugins.
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 the linked swift-java-weather-app/weather-lib/build.gradle and hello-swift-java/hashing-lib/build.gradle with the root swift-android.gradle.kts, then inventory the other sample build scripts. Decide how the examples should use one Gradle style and verify that the resulting scripts can share the intended root logic. Done means the sample build scripts are consistently standardized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, groovy, kotlin
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100