Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False-positive no-multi-spaces warnings on javadoc comments #706

Closed
carstenhag opened this issue Feb 25, 2020 · 1 comment · Fixed by #744
Closed

False-positive no-multi-spaces warnings on javadoc comments #706

carstenhag opened this issue Feb 25, 2020 · 1 comment · Fixed by #744
Labels

Comments

@carstenhag
Copy link

Expected Behavior

IMO, the multiple spaces aligning the parameters and their explanation help by making them easier to read.

Observed Behavior

In dozens of files this warning is shown. It is unreasonable to disable it per file. If I disable it globally though, I will miss things like SomeInterface {, which has too many spaces.

Steps to Reproduce

    /**
     * Gets Blabla from user.
     *
     * @param blabls12      1234
     * @param blabla123     6789
     * @param blabla        5678
     * @param longparam345  4567890
     * @param userId        567890
     * @return the user profile
     */

Your Environment

  • Version of ktlint used: Probably newest ktlint
  • Name and version (or code for custom task) of integration used (Gradle plugin, Maven plugin, command line, custom Gradle task): Gradle Plugin 9.2.1
@carstenhag
Copy link
Author

Thanks a lot for implementing this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants