Scaffold ck-notes crate with sealing preamble and design doc #49
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/049-scaffold-ck-notes-crate-with-sealing-preamble"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scaffold ck-notes crate with sealing preamble and design doc
Touches 6 files:
Cargo.lock,Cargo.toml,ck-notes/Cargo.toml,ck-notes/README.md,ck-notes/src/lib.rs,ckeditor-notes.md.Yes. The commit messages carried me through all 6 files, which is not always true.
@ -0,0 +49,4 @@| Gate | Target | Actual ||---|---|---|| Line coverage (`scripts/test.sh ck-notes --coverage`) | 100% | _scaffold — no code yet_ || Mutation kill rate (`scripts/test.sh ck-notes --mutants`) | ≥ 95% | _scaffold — no code yet_ |Where does the number beside
ratecome from? It reads as measured rather than chosen, and nothing on the line says which.@ -0,0 +50,4 @@//! commit is a skeleton — the preamble names the contract; subsequent//! commits land the code that earns it.#![deny(missing_docs)]I had to read
denytwice. Nothing wrong with it, but one line of comment would save the next person the second read.Comment added on
denyinck-notes/src/lib.rs. It was obvious when I wrote it and it will not be in a month.Measured. It is a named constant in
ck-notes/README.mdnow, with a line saying how.