Skip to content

Main content

Development: Editor Config Unset Property Token Tool

Recognize the EditorConfig unset value for one explicit property without reading files, inheritance or editor defaults.

Loading tool…

Description

Normalize an EditorConfig property and inspect its unset marker.

Build and configuration formats have dialect-specific quoting, whitespace and escaping rules. A local prefix or character transformation handles only the declared fragment, leaving full parsing, evaluation and precedence to the consuming implementation.

Normalize an EditorConfig property and inspect its unset marker.

When to use this tool

Use Development: Editor Config Unset Property Token when inspecting the stated text or configuration fragment.

How to use the tool and how it works

  1. Enter property, value. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Normalize an EditorConfig property and inspect its unset marker. Require ASCII alphanumeric/underscore property and nonempty single-line value; lowercase property and compare lowercased value with unset.1

Input fieldMeaning and unitsAccepted input
propertyPropertyRequired. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units.
valueValueRequired. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units.
Output fieldInterpretationReturned shape
resultReturned object; expand its named members below.Required. Object.
result.propertyPropertyCalculated result member: string.
result.unsetUnsetCalculated result member: boolean.
json
{
  "input": {
    "property": "Indent_Size",
    "value": "UNSET"
  },
  "output": {
    "result": {
      "property": "indent_size",
      "unset": true
    }
  }
}

Limitations and assumptions

  • No trimming, property-specific validation or configuration application occurs.
  • Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use the appropriate full parser and actual configuration context for reliable interpretation or application.

References

  1. Calculation and input contract: development/editor-config-unset-property-token — tool.io

Similar or alternative tools