Repository navigation
Stop comments and recipes naming ignored paths where nothing needs the path #313
Description
Part of #312.
Problem
Comments, citations and one recipe name gitignored paths although nothing depends on the path itself:
- comments describing cargo's build output as
target/…(Cargo.toml,thumb_ffmpeg.rs, severalJustfilecomments); - citations of installed npm and cargo dependencies by local file and line inside the install (
@wdio/tauri-service dist/esm/index.js:NNNN,@wdio/utils/build/index.js:NNN,tauri-plugin-wdio-webdriver … window.rs:NN, and others in the wdio configs and e2e specs); - a removed local worktree's path and a local log file's name in e2e spec comments;
- the
Justfilerunning prettier asnode_modules/.bin/prettier.
A citation into a local install cannot be followed by a reader who does not have that install at that version, and it goes stale on the next upgrade without anything noticing.
Desired outcome
- Each citation names the package, the version from the lockfile, and the symbol, verified against that version.
- Comments describe build output without naming the directory.
- The
Justfileruns the installed prettier throughnpm exec --no, which refuses to fetch, and reports npm's own error when it fails. - No line in scope names an ignored path. Lines whose fix needs a decision (where runtime data and build output live, the worktree recipe, conventions) stay for the issues that settle them.
Activity