nix: comments state current behaviour, not history
Rewrite comments and option descriptions under nix/ that narrate how the
code got here ("used to", "new name", "sat at the TOP", "no longer",
renamed/moved narration, attributions) to say what the code does now and
why. Comments and description strings only; no logic changes.
Files in open PR #4970's diff are left alone. Refs #3902
This commit is contained in:
parent
ea63b0d150
commit
1c90619fbb
45 changed files with 331 additions and 411 deletions
|
|
@ -5,10 +5,10 @@
|
|||
|
||||
# Pure vendored Swagger UI 5.17.14 static dist — no hyperhive theming
|
||||
# (see ./swagger-ui-theme.nix for that layer). Deliberately NOT sourced
|
||||
# via the Rust `utoipa-swagger-ui-vendored` crate / Cargo.lock (per the
|
||||
# operator's ask: a nix package that just contains the plain static
|
||||
# dist, not fetched via cargo) — hive-c0re no longer needs to know this
|
||||
# exists at all once the gateway hosts it directly.
|
||||
# via the Rust `utoipa-swagger-ui-vendored` crate / Cargo.lock: this is a
|
||||
# nix package that just contains the plain static dist, not fetched via
|
||||
# cargo — hive-c0re does not need to know this exists, because the
|
||||
# gateway hosts it directly.
|
||||
#
|
||||
# Sourced straight from the `swagger-ui-dist` npm package, which ships
|
||||
# exactly the built `dist/` files (no source, no build step needed) at
|
||||
|
|
|
|||
Loading…
Reference in a new issue