-
Notifications
You must be signed in to change notification settings - Fork 2
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 comments at 90 characters #5
Comments
cbeams
added a commit
to bisq-network/bisq-monitor-deprecated
that referenced
this issue
Mar 16, 2018
cbeams
added a commit
to bisq-network/bisq-common
that referenced
this issue
Mar 16, 2018
cbeams
added a commit
to bisq-network/bisq-statsnode
that referenced
this issue
Mar 16, 2018
cbeams
added a commit
to bisq-network/bisq-seednode
that referenced
this issue
Mar 16, 2018
cbeams
added a commit
to bisq-network/bisq-p2p
that referenced
this issue
Mar 16, 2018
cbeams
added a commit
to cbeams/bisq-pricenode
that referenced
this issue
Mar 16, 2018
cbeams
added a commit
to bisq-network/dao
that referenced
this issue
Mar 16, 2018
cbeams
added a commit
to bisq-network/bisq-core
that referenced
this issue
Mar 16, 2018
cbeams
added a commit
to bisq-network/bisq
that referenced
this issue
Mar 16, 2018
cbeams
changed the title
Wrap Javadoc at 90 characters
Wrap Javadoc and other comments at 90 characters
May 8, 2020
cbeams
changed the title
Wrap Javadoc and other comments at 90 characters
Wrap comments at 90 characters
May 11, 2020
cbeams
added a commit
to cd2357/bisq
that referenced
this issue
May 11, 2020
- Wrap comments at 90 chars per bisq-network/style#5 - Wrap code at 120 chars per bisq-network/style#3 - Remove unused imports - Remove extra newlines - Format code where appropriate - Remove unused Javadoc tags, e.g. @return, @param - End Javadoc summary sentence with a period where missing - Remove HTML formatting in Javadoc, e.g. extra <br>s
cbeams
added a commit
to cd2357/bisq
that referenced
this issue
May 11, 2020
- Wrap comments at 90 chars per bisq-network/style#5 - Wrap code at 120 chars per bisq-network/style#3 - Remove unused imports - Remove extra newlines - Format code where appropriate - Remove unused Javadoc tags, e.g. @return, @param - End Javadoc summary sentence with a period where missing - Remove HTML formatting in Javadoc, e.g. extra <br>s
cbeams
added a commit
to ghubstan/bisq
that referenced
this issue
May 18, 2020
cd2357
added a commit
to cd2357/bisq
that referenced
this issue
Jul 11, 2020
Update comments to reflect bisq-network/style#5 guideline
cd2357
added a commit
to cd2357/bisq
that referenced
this issue
Jul 20, 2020
Update comments to reflect bisq-network/style#5 guideline
cd2357
added a commit
to cd2357/bisq
that referenced
this issue
Jul 20, 2020
Update comments to reflect bisq-network/style#5 guideline
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#3 specifies that code should be wrapped at 120 characters, but prose in the form of comments is hard to read at that width. 90 characters is an ideal wrap margin for Javadoc and other comments, as it strikes a good balance between readability and accommodating longer literals like fully-qualified classnames, URLs, and so forth without requiring wrapping. Also, the ratio between 120-character code lines and 90-character Javadoc lines is aesthetically pleasing on its own.
Unfortunately, IDEA does not (yet) support enforcing multiple wrap margins, e.g. one for code lines and one for comment lines like Eclipse has done for years. But recent IDEA versions do support multiple visual guides, e.g. one at 120 for code and one at 90 for Javadoc. Our common IDEA code styles configuration has been updated to introduce the 90-character visual guide as a reminder about this.
See:
The text was updated successfully, but these errors were encountered: