Numeric Range Token Formatter
Format a validated ordered finite numeric pair as a start..end token; JavaScript canonical number spelling, not exact decimal-text preservation.
Description
Format a validated ordered finite numeric pair as a start..end token; JavaScript canonical number spelling, not exact decimal-text preservation.
A numeric-range token stores ordered endpoints separated by a double dot. Formatting does not imply an enumeration of values.
When to use this tool
Format a validated ordered finite numeric pair as a start..end token; JavaScript canonical number spelling, not exact decimal-text preservation.
- Prepare the supplied start, end 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 start, end. 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.token. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require end at least start and emit JavaScript numeric spellings joined by two dots.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| start | start. | Finite number |
| end | end. | Finite number |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.token | The token value under the stated formula or text convention. |
{
"input": {
"start": -2,
"end": 3.5
},
"output": {
"result": {
"token": "-2..3.5"
}
}
}Limitations and assumptions
- Input numbers must be finite and output-safe. The formatter does not select decimal precision, specify endpoint inclusivity or retain original textual precision.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use a parser for the actual target format when the task requires CSV, shell, URL, calendar or filesystem semantics. These tools implement the specific small grammars stated here, without adding those surrounding conventions.
References
Similar or alternative tools
- Numeric Range Token Parser
Parse one inclusive-shape numeric start..end token under strict decimal grammar; rejects backwards endpoints and does not enumerate the range.
- Integer Set Token Formatter
Format finite bounded integer values as a canonical sorted brace-delimited set token, omitting duplicate values.