Literal Key Value Line Formatter

Format a literal name-value line while rejecting delimiters inside its name to retain first-split reversibility.

Description

Format a literal name-value line while rejecting delimiters inside its name to retain first-split reversibility.

A key/value line can allow the separator inside its value when parsing always splits at the first separator.

When to use this tool

Format a literal name-value line while rejecting delimiters inside its name to retain first-split reversibility.

Prepare the supplied name, value, delimiter fields for this operation.
Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

Enter name, value, delimiter. Use the exact text syntax, units and index conventions explained below.
Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
Read result.line. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require a nonempty delimiter absent from name. Concatenate name, delimiter and value.^[1]

Input field	Meaning and representation	Accepted input
name	name.	Text; at most 8,192 UTF-16 code units, subject to the grammar above
value	value.	Text; at most 8,192 UTF-16 code units, subject to the grammar above
delimiter	delimiter.	Text; at most 8,192 UTF-16 code units, subject to the grammar above

Output field	Interpretation
result	Object containing the named outputs below.
result.line	The line value under the stated formula or text convention.

json

{
  "input": {
    "name": "a",
    "value": "b=c",
    "delimiter": "="
  },
  "output": {
    "result": {
      "line": "a=b=c"
    }
  }
}

Limitations and assumptions

No escaping or multiline restriction is added. Empty names/values are allowed and a delimiter inside value remains literal.
Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Alternative or Complementary methods

Choose the exact text grammar before combining serializers and parsers. UTF-16 record lengths, raw separators and custom backslash escapes differ from byte framing, CSV, Markdown and spreadsheet semantics.

References

Tool behavior and example: Literal Key Value Line Formatter — tool.io

Similar or alternative tools

Literal Key Value Line Parser
Split one literal name-value line at its first caller delimiter; does not trim, unquote or interpret escapes.
Key Value Block Duplicate Audit
Audit duplicate literal keys in an ordered key-value block without choosing first or last wins.