Standalone gradle plugins #48
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Generate changelog in
|
|
👍 |
|
Released 0.3.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this PR
We're spreading logic between baseline and this repo, and don't actually have a particularly simple usage story (we currently tell people to apply
com.palantir.baseline-formatand addcom.palantir.baseline-format.palantir-java-formatto theirgradle.properties)After this PR
==COMMIT_MSG==
The standalone
com.palantir.java-formatplugin provides aformatDifftask. IntelliJ setup has been moved to acom.palantir.java-format-ideaplugin.==COMMIT_MSG==
This should hopefully reduce the coupling between baseline & this repo and make it easier for people to just try out our formatter if they want to.
Possible downsides?
palantirJavaFormat()merged into spotless upstream??