Filename Extension Chain Replacer
Replace the complete literal extension chain while preserving the leading-dot-aware stem; an empty extension list removes the chain.
Description
Replace the complete literal extension chain while preserving the leading-dot-aware stem; an empty extension list removes the chain.
An extension chain treats every dot segment after the first eligible dot as an extension, preserving a leading dot in the stem.
When to use this tool
Replace the complete literal extension chain while preserving the leading-dot-aware stem; an empty extension list removes the chain.
- Prepare the supplied name, extensions 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, extensions. 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.name. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Split name under that rule, require each replacement extension nonempty and free of dot, slash and NUL, then join the unchanged stem with the new chain. An empty replacement list removes the chain.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| name | name. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| extensions | extensions. | At most 128 strings, each at most 128 UTF-16 code units |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.name | The name value under the stated formula or text convention. |
{
"input": {
"name": "archive.tar.gz",
"extensions": [
"zip"
]
},
"output": {
"result": {
"name": "archive.zip"
}
}
}Limitations and assumptions
- This is text manipulation, without file-type detection or filesystem changes. Backslashes have no separator role under the POSIX convention.
- 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.
- String lists have at most 128 entries of at most 128 code units; matrices have at most 128 rows and columns. Larger numeric lists and parsed JSON have separate bounded budgets. 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 filesystem-aware implementation with appropriate platform semantics for actual file operations. Literal slash components, Unicode comparison and filename plans do not resolve symlinks or atomically reserve a destination.
References
Similar or alternative tools
- Filename Extension Chain Splitter
Split a filename into stem and all literal extension-chain segments after its first nonleading dot; no MIME inference.
- Leading Dot Filename Extension Split
Split the final filename extension while preserving a leading-dot-only name as extensionless; a trailing dot gives an empty extension.