[ci] formatting #2798
Merged
[ci] formatting #2798
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
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.
formatting now enabled. did the best I could to preserve items that do not format the best such as select statements in tests throughout. Its possible some where missed. I have drafted 3.5.12 release and note there but also will update read me to note that. This hasn't been a specific issue on the extension projects but was more prevalent here.
Blocking any code with '// @Formatter:off' and '// @Formatter:on' will lock the formatting self applied. Some of this I did on javadocs which probably have a better javadoc friendly way to resolve so hopefully we can eventually work these out so they don't need to exist after seeing how that can be addressed in each case.