comments

Comments in code

🧀 Avoid comments

Comments are code smells because they go out-of-date, bloat context, and lead to confusion.

Don't reference existing comments in the codebase – follow these rules

• Avoid adding comments – always prefer good names (explainer variables, functions, tests)
• Use test names to describe behaviour – unit tests are living documentation
• Good code explains itself – don't add comments that duplicate what the code already conveys

💡 Treatments

When code isn't clear, make it clearer:

• Rename variables and functions to make comments unnecessary
• Extract variables and functions to improve readability
• Use assertions to explain behaviour

Use test names to explain non-obvious details

❌ Bad

it("diffs the current value against resolved when targeted", () => {
  const { result } = renderHook(() => useJsonEditor(makeProps()));
  act(() => result.current.setDiffTarget("resolved"));
  // Current equals resolved → every line is unchanged.
  expect(result.current.diffJson.every((l) => l.state === "none")).toBe(true);
});

✅ Good

it("resets the state of every line when the diff is resolved", () => {
  const { result } = renderHook(() => useJsonEditor(makeProps()));
  act(() => result.current.setDiffTarget("resolved"));
  expect(result.current.diffJson.every((l) => l.state === "none")).toBe(true);
});

Let code speak for itself

❌ Bad

/* Whether the filter trigger should be displayed */
showFilter: boolean;

✅ Good

showFilter: boolean;

Replace comments with explainer variables

Move the comment into a variable name:

Before

// NB `app.trustchain` is an encrypted db path: while the app is password-locked it reads back
// as the ciphertext string. Importing it would regenerate member credentials and null the
// trustchain (LIVE-36130). IsUnlocked re-runs this thunk once the encryption key is set.
// `undefined` must still go through: that is the legitimate "nothing persisted" case.
if (typeof data === "string") return;