Code Formatter

[KronicDeth]

Resolves #98

Changelog

Enhancements

• Code Formatter
  • do block lines are indented
  • do blocks end as the last argument of a no parentheses call unindents to the start of the call
  • If one clause of a multi-clause anonymous function wraps, all clauses wrap.
  • Indent after else
  • Indent map and struct keys
  • All keys wrap if any key wraps
  • No spaces around...
    • .
  • Spaces around...
    • and
    • in
    • or
    • when
  • Configure spaces around...
    • =
    • <- and \\
    • !=, ==, =~, !==, and ===
    • <, <=, >=, and >
    • + and -
    • * and /
    • Unary +, -, !, ^, and ~~~
    • ->
    • ::
    • |
    • || and |||
    • && and &&&
    • <~, |>, ~>, <<<, <<~, <|>, <~>, >>>, and ~>>
    • ..
    • ^^^
    • ++, --, .., <>
    • =>
  • Configure spaces before...
    • ,
  • No space after...
    • @
  • Spaces after...
    • not
    • fn
    • after
    • catch
    • rescue
    • key:
  • Configure space after...
    • &
    • ,
  • Configure spaces within...
    • { }
    • << >>
    • [ ]
    • ( )
  • No space around / in &NAME/ARITY and &QUALIFIER.NAME/ARITY
  • when wraps when its right operand wraps, so that guards start with when on a newline when they are too long.
  • Align |> at start of indented line for pipelines
  • Align end with start of call instead of start of line for do blocks in pipelines
  • Indent list elements when wrapped
  • Indent tuple elements when wrapped
  • Align type definition to right of ::
  • Align guard to right of when when guards span multiple lines
  • Align two operator (++, --, .., <>) operands, so that <> binaries are multiple lines align their starts instead of using continuation indent and being indented relative to first operand.
  • Align pipe | operands, so that alternates in types and specs are aligned instead of continuation indented relative to the first operand.
  • Comments in spec (that is above operands to | align with the operands
  • Remove newlines from pipelines, so that all pipelines start with an initial value or call and each |> is the start of a successive line.
  • Key exclusivity: if an association operation or keyword key is already on a line, the container value automatically has it's elements wrapped if there is nested associations or keyword pairs, so that two levels of keys are not on the same line.
  • Indent bit string (<< >>) elements when wrapped