Fix JavadocTagContinuationIndentation in AfterBeforeParameterResolver #3566
Conversation
This file contains hidden or 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.
Fix JavadocTagContinuationIndentation in AfterBeforeParameterResolver
Summary
This PR fixes JavadocTagContinuationIndentation violations in
pgjdbc/src/testFixtures/java/org/postgresql/test/impl/AfterBeforeParameterResolver.javathat will occur with the latest Checkstyle update.Motivation
A build failure was detected in
AfterBeforeParameterResolver.javawhere the Javadoc comments have inconsistent indentation, violating theJavadocTagContinuationIndentationCheckin the latest Checkstyle version.Details
Corrected the indentation in Javadoc comments to comply with
JavadocTagContinuationIndentationCheckrules.Implementation Notes
This PR should be merged after we release the new Checkstyle version and
pgjdbcupgrades to it. Without this change, existing code that was previously compliant may fail validation checks.