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

Wrap all lines longer than 100 characters #83

Closed
bonaparten opened this issue Nov 18, 2020 · 1 comment · Fixed by #148
Closed

Wrap all lines longer than 100 characters #83

bonaparten opened this issue Nov 18, 2020 · 1 comment · Fixed by #148
Assignees
Labels
code quality Topics around code quality, e.g. refactoring, better naming of methods/classes

Comments

@bonaparten
Copy link
Contributor

bonaparten commented Nov 18, 2020

Every line in code should be wrapped by the 100th character at the latest. There are some lines with the annotation @link in javadoc which contain more than 100 characters. See #82

@bonaparten bonaparten added the documentation Improvements or additions to documentation label Nov 18, 2020
@bonaparten bonaparten changed the title Split by 100th character at the latest in javadocs Split by the 100th character at the latest in javadoc Nov 18, 2020
@FabiKo117 FabiKo117 added this to To do in ohsome API general via automation Nov 18, 2020
@tyrasd tyrasd added code quality Topics around code quality, e.g. refactoring, better naming of methods/classes and removed documentation Improvements or additions to documentation labels Nov 18, 2020
@tyrasd tyrasd changed the title Split by the 100th character at the latest in javadoc Wrap all lines longer than 100 characters Nov 18, 2020
@bonaparten bonaparten self-assigned this Jan 27, 2021
@bonaparten
Copy link
Contributor Author

So far I have not found a solution. In Eclipse, it is possible to wrap lines with the @link annotation (and the links still work) but saving, eclipse autocorrects the change unwrapping the lines. It could be possible to use @formatter:off to deactivate the formatter for selected code areas but I find this solution ugly.

ohsome API general automation moved this from To do to Done Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code quality Topics around code quality, e.g. refactoring, better naming of methods/classes
Projects
2 participants