Text Diff for Config Changes and Review
Use this page when the job is comparing two text versions, understanding what changed, and deciding whether a deterministic share URL or explicit share state is appropriate.
Keep the scope tied to the current diff checker: line-by-line review, preset examples, POST-first privacy for custom text, and optional explicit share URLs only when they fit safely.
Use this when
A rollout, API contract, or editorial change needs a line-by-line review before you send the result to another person.
What to inspect first
Compare the summary counts, rule settings, and current share mode before you worry about deeper diff interpretation.
Guardrail
Custom text stays POST-first by default. Use a deterministic share URL only for presets or when the explicit share state is small enough to travel safely.
Config rollout
Start from a safe environment-config example when the real job is understanding which setting changed.
LOG_LEVEL=info
...
LOG_LEVEL=debug
API response review
Compare structured payload snapshots when one field addition or plan change should stand out immediately.
{"status":"ok"} -> {"status":"ok","region":"us-east-1"}
Editorial pass
Use a short content revision when the review is about wording changes, not source control history.
Ship notes faster -> Ship release notes faster
The added, removed, and unchanged counts explain the overall shape of the diff before you scroll through every line.
- Ignore whitespace or case only when those differences are noise for the current review.
- Use the result summary to explain the change set before sharing the full line output.
Preset comparisons can stay deterministic and shareable, while custom comparisons should remain private unless you explicitly decide to copy the current text into a URL.
- Use the default safe share URL for presets when another reviewer needs the same baseline example.
- Use the explicit share URL only when the current comparison is small enough and intentionally shareable.