From c38d877b94c6ac5df2de4c9c939ae683d733e8b8 Mon Sep 17 00:00:00 2001 From: Owen Jacobson Date: Mon, 23 Jun 2025 22:45:18 -0400 Subject: Organize the developer docs into a "Pilcrow for Developers" book. The audience for this is developers looking to make changes to Pilcrow, either on the server, on the included client, or via its data model. Most of the material here is drawn from existing documents, but organized somewhat more coherently. I've left some space for client documentation, though no such documents exist yet. --- docs/linting.md | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 docs/linting.md (limited to 'docs/linting.md') diff --git a/docs/linting.md b/docs/linting.md deleted file mode 100644 index 47420bb..0000000 --- a/docs/linting.md +++ /dev/null @@ -1,21 +0,0 @@ -# Linting - -We use automated tools, rather than human effort, to spot possible bugs or dubious structural choices, where possible. This is handled by three tools: - -- Javascript is linted using [eslint]. -- Rust is linted using [cargo check] and [clippy]. - -[eslint]: https://eslint.org/ -[cargo check]: https://doc.rust-lang.org/cargo/commands/cargo-check.html -[clippy]: https://doc.rust-lang.org/cargo/commands/cargo-clippy.html - -## Tools - -- To check for detectable lints, run - `tools/check-lint`. This should be run whenever making changes, and is part of the optional - `git-hooks/pre-commit` hook script. - -- To fix lints that have automatic fixes, run - `tools/delint`. - -You can also run the individual lint tools directly. The tool scripts listed above contain the specific commands needed. -- cgit v1.2.3