Skip to content

Implement rules to track length and breaking of lines #73

@jvsqzj

Description

@jvsqzj

Defining requirements for Line Length and Breaking as detailed in DML style guide:

Pending:

  • LL2 Break long lines before binary operators, not after - @jvsqzj
  • LL3 Break conditional expressions before the ?, or both before the ? and before the : - @dtarassenko
  • LL4 Following lines should be indented at their natural position. Add parentheses if it makes indenting easier. May also add spaces in expressions to make them line up
  • LL5 Break long method declarations with output parameters before the arrow - @alecalvop
  • LL6 Function and method invocations can be broken after the opening parenthesis, with the continuation lines indented one level - @me-cr

Implemented:

  • LL1 Lines should be kept shorter than 80 characters. Longer lines wrap or become partially invisible in editors whose windows have the standard width of 80 columns, which makes the code much harder to read

Some of these are related to indentation rules.

Metadata

Metadata

Assignees

No one assigned

    Labels

    LinterWork or bugs relating to the linting functionalityenhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions