This file live in a distinct source-paths so it's not affected by the Reloaded workflow,
while developing formatting-stack itself.

A set of defaults apt for formatting/linting a git branch
(namely, the files that a branch has modified, respective to another).

See also: `formatting-stack.defaults`, `formatting-stack.project-formatter`

A set of defaults apt for frequent usage.

See also: `formatting-stack.branch-formatter`, `formatting-stack.project-formatter`

Ensures that no three consecutive newlines happen in a given file.

That can happen naturally, or because of other formatters' intricacies.

This formatter removes 'trivial' duplicate libspecs from the `ns` form.

Compensates for some `refactor-nrepl.clean-ns` intricacies, and also provides .cljs compatibility.

Holds a cache for the entire classpath, to make better use of the project-wide analysis capabilities.

Only needs to be created once, as the classpath never changes.

Observes these guidelines: https://stuartsierra.com/2015/05/10/clojure-namespace-aliases

This linter ensures that there's exactly once classpath resource per namespace and extension.

Note that generally it's fine to define identically-named Clojure/Script namespaces with _different_ extensions,
so that is allowed.

A test runner meant to be integrated with VCSs. JVM-only, and only `clojure.test` is targeted.

This test runner gathers Clojure ns's out of filenames, derives _even more_ testing ns's out of them
(via naming variations, project-wide `:require` analysis, and metadata analysis),
and invokes `#'clojure.test/run-tests` out of that result.

A set of defaults apt for formatting/linting a whole project.

See also: `formatting-stack.branch-formatter`, `formatting-stack.defaults`

Writes the output to a file which can be observed with e.g. `watch --color -n 1 cat .formatting-stack-report`.

Outputs report similar to github.com/xojs/xo

Prints an optionally colorized, indented, possibly truncated output of the reports.

Strategies are concerned with generating a seq of filenames to process (format, lint, or compile).

Said filenames must satisfy the `::protocols.spec/filename` spec, and represent an existing file.

They are configured to run in a determinate order.

In practice, a strategy is function that receives a seq of filenames, and returns another:

* more filenames may be added; and or
* the passed filenames may be `filter`ed.

A strategy may not return nil.

Functions for `git diff --name-status` parsing.

Note that commands such as `git status`, `git ls-files` do not share its output format.

Functions for `git status` parsing. Note that commands such as `git diff`, `git ls-files` do not share its output format.