Skip to content

issue #426 Description of the coding style #502

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

Merged
merged 4 commits into from
Oct 4, 2012
Merged

issue #426 Description of the coding style #502

merged 4 commits into from
Oct 4, 2012

Conversation

awulder
Copy link

@awulder awulder commented Sep 8, 2012

Issue #426 Description of the coding style

Issue #426 Description of the coding style
## Tabs and Indents

* Tab size : 4
* Indent : 4
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this hand-written, or exported from a tool?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's hand written

@dsaff
Copy link
Member

dsaff commented Sep 11, 2012

Could we then get the whitespace to line up in the coding style doc? Sorry to be a stickler.

@awulder
Copy link
Author

awulder commented Sep 11, 2012

Do you want to align the numbers or do I just have to remove the whitespaces? I have searched for a way to align the numbers in markdown but there isn't a simple way of doing it.

@dsaff
Copy link
Member

dsaff commented Sep 12, 2012

I guess I don't understand the current use of whitespace--it doesn't seem to be pegged to tab stops, and it doesn't seem to be a constant number of spaces between each colon and number. If I were reading the doc in text, I think I'd either want all the numbers in a clump to start at the same column, or at least just have a single space between each colon and number.

Or is there a significance to the number of spaces that Markdown is using?

Issue #426 Removed confusing whitespaces.
@awulder
Copy link
Author

awulder commented Sep 12, 2012

Markdown ignores the spaces. I removed the confusing spaces you mentioned.


## Blank Lines

### Keep Maximum Blank Lines
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does "Keep Maximum Blank Lines" mean?

Removed the Markdown syntax, changed import order and removed confusing
Maximum Blank Lines section.
@awulder
Copy link
Author

awulder commented Sep 13, 2012

I removed all the Markdown syntax, changed the import order (copied the wrong one) and removed the Maximum Blank Lines section. Maximum Blank Lines means for example if you have three blank lines in your method and you have set the maximum to two then the code fails the coding style. Since it's confusing I removed it.

* After description

Invalid tags
* Keep empty @param tags
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't want to keep empty javadoc tags that add no information.

@dsaff
Copy link
Member

dsaff commented Sep 17, 2012

Getting close, thanks!

- Do not align JavaDoc parameter description
- Removed "Keep empty .. JavaDoc tag"
- corrected typp
dsaff pushed a commit that referenced this pull request Oct 4, 2012
issue #426 Description of the coding style
@dsaff dsaff merged commit 68cc61e into junit-team:master Oct 4, 2012
@dsaff
Copy link
Member

dsaff commented Oct 4, 2012

Thanks, and sorry for the delay!

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

Successfully merging this pull request may close these issues.

2 participants