TeamAmaze / TeamAmaze/AmazeFileManager
spotlessApply should format Kotlin source code instead of failing build when code is not of standard
Open
Nobody has claimed this yet.
Area-CodeHealth
Issue-Feature
Issue-Task (low)
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Currently during build, when spotlessApply finds a Kotlin source code doesn't fits the standard, it will fail the build instead of step up and format the code for the developer. It should format the Kotlin source code files like the Java source code do.
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 the Spotless configuration and the spotlessApply entry point used for Kotlin sources. Compare its behavior with Java formatting, then verify that nonstandard Kotlin code is formatted successfully rather than failing the build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100