Path Component Redaction Tool
Redact explicitly indexed nonempty raw slash components while preserving empty segments and terminal separators.
Description
Redact explicitly indexed nonempty raw slash components while preserving empty segments and terminal separators.
A textual path redaction can replace selected nonempty slash-separated components while retaining separator structure.
When to use this tool
Redact explicitly indexed nonempty raw slash components while preserving empty segments and terminal separators.
- Prepare the supplied path, componentIndexes, replacement 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 path, componentIndexes, replacement. 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.path. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require replacement to be one nonempty slash/NUL-free component. Number only nonempty input components from zero, replace selected indexes and rejoin the original split positions with slashes.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| path | path. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| componentIndexes | component indexes. | List of finite numbers; bounded by the operation |
| replacement | replacement. | 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.path | The path value under the stated formula or text convention. |
{
"input": {
"path": "/a/b/",
"componentIndexes": [
1
],
"replacement": "X"
},
"output": {
"result": {
"path": "/a/X/"
}
}
}Limitations and assumptions
- Repeated and terminal separators remain. The source path is not resolved, decoded or accessed, and replacement alone does not guarantee all sensitive data is removed.
- 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
- Path Component Name Budget Checker
Audit lexical POSIX component UTF-8 byte budgets against an explicit limit; not a universal NAME_MAX or filesystem encoding claim.
- Relative Path Component Resolver
Lexically resolve a relative POSIX path against an absolute directory with dot collapse; no symlink or actual-file resolution.