Break into spotless-lib (reusable for other projects) and spotless-gradle
See original GitHub issueSpotless now has quite a few utilities for mass string manipulation which are useful outside of a gradle plugin:
- ensuring idempotency, and working around it when there are bugs
- writing functions in an easy-to-serialize way
If we break the core functionality into spotless-lib, that would allow spotless-maven, etc. It would also speed up the spotless test suite by relying less on the excellent but slow gradle testkit. Going to explore this in the spotless-lib
branch.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:18 (18 by maintainers)
Top Results From Across the Web
diffplug/spotless - Gitter
If you want Spotless to leave generated sources alone, and format them in a different folder, you'll need to copy the generated sources...
Read more >Spotless Gradle - Visual Studio Marketplace
Extension for Visual Studio Code - Format your source files using Spotless via Gradle.
Read more >Spotless - Gradle - Plugins
Common Gradle Spotless plugin conventions used by tailrocks projects. ... Preconfigured spotless configuration and gradle tasks for use in other projects.
Read more >Spotless on Android - Medium
It is as simple as creating a spotless.gradle file (you can give it any name) ... our project and then, again, in the...
Read more >Spotless Gradle - IntelliJ IDEs Plugin - JetBrains Marketplace
An IntelliJ plugin to allow running the spotless gradle task from within the IDE on the current file selected in the editor. You...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks perfect as-is. The gradle integration test is prrroobably overkill for future rules that get added when there’s a nice test in lib, but it’s nice to have a few end-to-end checks in the test suite. Well done!
IndentStepTest has been migrated as of https://github.com/diffplug/spotless/commit/2ff03646f1baf64421068090113c39552432e8a5.