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

New Rule T0016: Separate declarations by an empty line #9130

Closed
pavel-mikula-sonarsource opened this issue Apr 18, 2024 · 0 comments · Fixed by #9147
Closed

New Rule T0016: Separate declarations by an empty line #9130

pavel-mikula-sonarsource opened this issue Apr 18, 2024 · 0 comments · Fixed by #9147
Assignees
Labels
Type: Tooling Tools make us productive.
Projects

Comments

@pavel-mikula-sonarsource
Copy link
Contributor

pavel-mikula-sonarsource commented Apr 18, 2024

The boundary between different member types should be an empty line (like between last field and first property, except abstract members).

These non-abstract members should be separated by empty line:

  • Enums
  • Multi-line properties
  • Multi-line events
  • Multi-line indexers
  • Constructors
  • Destructor
  • Methods
  • Conversion operators
  • Operators
  • Nested types

It does not apply to:

  • Constant fields (syntax-wise, it's a single-line field)
  • Fields
  • Single-line properties
  • Single-line event fields
  • Single-line indexers
  • Delegate declaration
  • Abstract members
@pavel-mikula-sonarsource pavel-mikula-sonarsource created this issue from a note in Best Kanban (To do) Apr 18, 2024
@pavel-mikula-sonarsource pavel-mikula-sonarsource moved this from To do to In progress in Best Kanban Apr 18, 2024
@pavel-mikula-sonarsource pavel-mikula-sonarsource changed the title New Rule T0016: Separate members by an empty line New Rule T0016: Separate declarations by an empty line Apr 18, 2024
@github-actions github-actions bot moved this from In progress to Review in progress in Best Kanban Apr 19, 2024
@github-actions github-actions bot moved this from Review in progress to In progress in Best Kanban Apr 19, 2024
@github-actions github-actions bot moved this from In progress to Review in progress in Best Kanban Apr 19, 2024
@github-actions github-actions bot moved this from Review in progress to Review approved in Best Kanban Apr 19, 2024
Best Kanban automation moved this from Review approved to Validate Peach Apr 24, 2024
@pavel-mikula-sonarsource pavel-mikula-sonarsource moved this from Validate Peach to Done in Best Kanban Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Tooling Tools make us productive.
Projects
Best Kanban
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants