Space to JSON array

The transformation is fully specified and has no options. The input is split on a whitespace-run pattern, each fragment is trimmed, empty fragments are discarded, and the surviving fragments are serialised as a JSON array of strings with two-space indentation.

Every part of that sentence is a decision with consequences, and the rest of this page is those consequences. The work runs client-side in JavaScript, so there is no upload, no element cap and no run limit.

The distinction between splitting on one space character and splitting on a run of whitespace shows up immediately on real input. Split on a single space and "alpha beta" yields three fragments, the middle one empty. Split on a run and it yields two.

This route uses the run form, so consecutive spaces, tabs, line feeds and carriage returns collapse into one boundary. The practical effect is that input pasted from a terminal, a wrapped message or a spreadsheet cell needs no preprocessing. Documented competitors that split on a literal single space do not behave this way, and the difference is visible in the element count rather than hidden.

Verification belongs in the procedure, not after it.

Step 1

Paste the list in whatever spacing it arrived with. Irregular separators are handled by the delimiter semantics above.

Step 2

Run the conversion, which is a local, synchronous transformation.

Step 3

Compare the element count with the number of intended values. A surplus indicates a value containing internal whitespace, which is the only failure this route can produce silently.

No type inference is performed. Numeric-looking fragments, the literals true and false, and null all serialise as strings. "42 true null" produces three string elements, not a number, a boolean and a null.

Inference is the wrong default for a flat list because it is lossy and irreversible in exactly the cases that matter. An identifier of 0042 parsed as a number loses its padding, a version string of 1.10 collapses to 1.1, and a value in exponential form is rewritten entirely. Casting a known subset of elements downstream is cheap; detecting which elements were silently rewritten is not.

Serialisation goes through the standard JSON serialiser, so escaping is not hand-rolled. A fragment containing a double quote is emitted with the quote escaped, a fragment containing a backslash is emitted with it doubled, and the resulting document parses without intervention.

Encoding is preserved as well. Accented Latin text and CJK characters are emitted unchanged rather than escaped into surrogate sequences or stripped, so round-tripping the output through a parser returns the original strings.

Each of these is a feature some competing converter offers. None of them exists here, and the honest answer is more useful than an ambiguous one.

Deduplication

Not implemented. Repeated fragments produce repeated elements, in input order. Deduplication is a separate route.

Empty-element preservation

Not available. Empty fragments are filtered unconditionally, so an intentional empty string cannot be emitted.

Compact serialisation

Not offered. Indentation is fixed at two spaces. The JSON minifier route produces the compact form.

Structured output

No objects, no nesting, no key-value emission. Tabular input belongs with a CSV converter.

Ingest features

No file import, no batch, no API, no saved configuration.

Whitespace is a poor delimiter for any value that contains whitespace, which is most human-readable text: names, titles, addresses, sentences. On such input this route is not malfunctioning when it produces one element per word, it is doing exactly what a whitespace delimiter means.

Fixed-delimiter routes exist for comma, semicolon, colon, pipe, slash, tab, caret, tilde and double space, and a custom delimiter route accepts an arbitrary string. Selecting the route that matches the data is strictly better than repairing a wrong split afterwards.

The applications are all cases where a list exists in an informal medium and is needed in a machine-readable one.

Configuration authoring

Promoting a list of flags, hosts or identifiers from a message or a shell history into an array literal.

Fixture construction

Producing deterministic test data from a list supplied in a ticket, without hand-quoting each element.

Request body assembly

Building an array parameter for an API call where a quoting error is otherwise the likeliest defect.