Single Pass Literal Template Renderer

Render a single pass of literal placeholders from an explicit unique name/value table; inserted placeholders are not recursively expanded.

Description

Render a single pass of literal placeholders from an explicit unique name/value table; inserted placeholders are not recursively expanded.

Literal template substitution replaces named placeholders without executing expressions. A single pass prevents replacement text from introducing new substitutions during the same run.

When to use this tool

Render a single pass of literal placeholders from an explicit unique name/value table; inserted placeholders are not recursively expanded.

  • Prepare the supplied text, openMarker, closeMarker, names, values 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

  1. Enter text, openMarker, closeMarker, names, values. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.text, result.unresolvedNames. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require nonempty markers and aligned names/values with distinct nonblank names. Scan the original text for an opener followed by the next closer, replace known names, retain unknown placeholders and list their names.1

Input fieldMeaning and representationAccepted input
texttext.Text; at most 8,192 UTF-16 code units, subject to the grammar above
openMarkeropen marker.Text; at most 8,192 UTF-16 code units, subject to the grammar above
closeMarkerclose marker.Text; at most 8,192 UTF-16 code units, subject to the grammar above
namesnames.At most 128 strings, each at most 128 UTF-16 code units
valuesvalues.At most 128 strings, each at most 128 UTF-16 code units
Output fieldInterpretation
resultObject containing the named outputs below.
result.textThe text value under the stated formula or text convention.
result.unresolvedNamesThe unresolved names list in the ordering and representation described above.
json
{
  "input": {
    "text": "{a}{b}",
    "openMarker": "{",
    "closeMarker": "}",
    "names": [
      "a"
    ],
    "values": [
      "{b}"
    ]
  },
  "output": {
    "result": {
      "text": "{b}{b}",
      "unresolvedNames": [
        "b"
      ]
    }
  }
}

Limitations and assumptions

  • Inserted values are never rescanned. An unclosed opener leaves the remaining original text unchanged; there is no escaping, nesting, evaluation or output-context sanitization.
  • Text offsets and lengths use UTF-16 code units unless explicitly described as bytes or code points. CRLF, CR and LF are recognized as line endings; a terminal newline creates a final empty line in the shared line model.
  • 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.
  • Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
  • 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

Use a parser or language-aware editor when quoting, syntax or nested constructs matter. For plain text transforms, keep UTF-16 offsets, Unicode code points, grapheme clusters and UTF-8 byte offsets distinct; apply changes to the same source version used to calculate spans.

References

  1. Tool behavior and example: Single Pass Literal Template Renderer — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies