Skip to content
Developer Failure Diagrams

Worked example · No account needed

Three physical lines.
One data row.

A quoted line break belongs to a field. A newline split loses that boundary before your comparison even starts.

The exact synthetic fixture

id,note\r\n7,"first line\r\nsecond line"

Here \r\n denotes a CRLF line break. The downloaded file contains real CRLF bytes, not those four printed characters, and no final newline.

Physical lines: 3. Parsed CSV records: 2, including the header. Data rows: 1. The note is one field containing an embedded CRLF.

Failure: split a quoted CRLF into two rows and report a false mismatch. Alternative: choose dialect, parse quoting, retain the embedded break and validate actual records.
Open the full-size diagram · Dark version

Use the diagram with its boundary

  1. State the dialect: comma-separated, double-quote enclosure, CRLF.
  2. Parse records with a CSV parser instead of splitting lines.
  3. Keep the header separate when counting data rows.
  4. Review column counts and business values after parsing.

RFC 4180 describes quoted fields with line breaks; it is informational and dialects differ. This illustration does not validate a migration or make spreadsheet formulas safe.

Edit the original labels

Download the sample, read README.md and LICENSE.txt, then change scenes.json. With Node 22+, run:

node render.mjs scenes.json my-edited-assets

The output folder must be new. The fixed layout accepts four short steps per lane; shorten overlong text and preview both themes after editing. The renderer is not a general graph editor.

Get the fixture, source and diagramsBack to all free scenarios

Related tools

Explore the existing CSV check preview · Explore the existing JSON masking preview. These are separate tools; this asset pack does not include their engines.