Orkuncakilkaya
334469ef61
lint lines in package.ludic - one_statement, max_file_lines, max_function_lines, max_comment_lines, max_header_lines, paths, baseline - checked by ludic-fmt --check <files> and ludic-fmt --lint (the project), at the line; a baseline ratchet lets a rule arrive in a codebase that breaks it (--init-baseline), lowered as it is fixed. check-impl reads the alias declarations too (it had been blind to every namespace L6 moved out of the compiler), and eight methods get their pages; a test holds the formatter to keeping type arguments together (L5). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
7 lines
492 B
Markdown
7 lines
492 B
Markdown
bump: minor
|
|
type: feature
|
|
**`ludic-fmt` enforces a project's style.** `lint` lines in `package.ludic` state it - one statement
|
|
per line, file, function and comment-block limits (a file's opening comment its own) - and
|
|
`ludic-fmt --check <files>` and `ludic-fmt --lint` (the project's paths) fail what breaks them, at the
|
|
line. A baseline file is the ratchet that lets a rule arrive in an existing codebase: the counts a
|
|
file had may stay but not grow, and they are lowered as they are fixed.
|