Finding
Text, a regular expression, or a JSONPath — over one document or a thousand records.
In the app
Find (⌘F) takes words, a /regex/ or a JSONPath and lights the matching values in the tree; over records it counts the source lines.
Filter, on records, is a bar in Find’s shape: the text box, the level chips as a track, broken only, and the measured count. Opening one closes the other.
Across the two shapes
A verb is implemented once per shape, not once per format. That is why a CSV gets the same tools as a webhook payload: both collapse to one of two shapes before any verb runs.
How the shapes differ for search: Records adds numeric aggregates.
- document · JSON, YAML, XML
- records · NDJSON, CSV, TSV, Markdown table, Log
A worked example
Four queries over the API-response sample, counted when this page was built. Text is case-insensitive by default; a regex is a regex; a JSONPath returns the values at the path.
- text “oak” · 2 hits
- regex /^BRD-/ · 1 hit
- JSONPath $.items[*].sku · 2 hits
- text “brooklyn” · 1 hit