Fix: Disable conflicting checkstyle rules if started migrating to PJF #1064
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
iamdanfox
approved these changes
Nov 21, 2019
|
Released 2.35.2 |
This was referenced Nov 21, 2019
This was referenced Nov 21, 2019
This was referenced Nov 29, 2019
This was referenced Dec 16, 2019
This was referenced Jan 16, 2020
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
Excavator PRs that start migrating repos to palantir-java-format (but don't convert all files in one go) run into checkstyle errors because there is a check that conflicts with PJF style.
After this PR
==COMMIT_MSG==
Allow declaring that conversion to palantir-java-format has been started, which ensures that conflicting checkstyle rules are removed.
==COMMIT_MSG==
Possible downsides?