Enclosing Literal Wrapper Stripper
Strip one complete nonoverlapping enclosing literal wrapper, never internal or partial matches.
Description
Strip one complete nonoverlapping enclosing literal wrapper, never internal or partial matches.
An enclosing wrapper consists of a prefix and suffix surrounding the entire text. Removing exactly one verified pair is safer than trimming matching characters indiscriminately.
When to use this tool
Strip one complete nonoverlapping enclosing literal wrapper, never internal or partial matches.
- Prepare the supplied text, prefix, suffix 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 text, prefix, suffix. 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.stripped, result.text. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require nonempty prefix/suffix. Strip them only when text is long enough for both without overlap and begins/ends with the exact respective literals; otherwise return the original text and stripped false.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| text | text. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| prefix | prefix. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| suffix | suffix. | 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.stripped | Flag for stripped under the exact condition described above. |
| result.text | The text value under the stated formula or text convention. |
{
"input": {
"text": "[a]",
"prefix": "[",
"suffix": "]"
},
"output": {
"result": {
"stripped": true,
"text": "a"
}
}
}Limitations and assumptions
- Only one outer pair is removed. Whitespace, nested wrappers and partial matches are preserved; the tool does not parse brackets or quoted-string escape rules.
- 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
Similar or alternative tools
- Leftmost Longest Literal Match Selector
Select nonoverlapping leftmost-longest literal alternatives; equal lengths retain input alternative order.
- Overlapping Literal Match Indexes
Return overlapping literal-match UTF-16 offsets; distinct from a nonoverlapping replacement operation.