Supported EditorConfig Pair Resolver

How to use Supported EditorConfig Pair Resolver

Resolve EditorConfig source pairs for explicit virtual files using a bounded selected ASCII glob/path profile with root, precedence and unset witnesses. Trace common file sections and comma brace alternatives across supplied parent and child sources. This reports matched source values; editor defaults and derived indentation settings are deliberately unassessed.

1. Provide virtual editorconfig sources and target paths as json.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• Input is one explicit JSON bundle of 1–16 {directory,source} virtual files and 1–25 unique target file paths. Source JSON is capped at 200 KB and combined decoded configuration contents at 100 KB. Paths use canonical relative POSIX spelling, at most 1,024 UTF-8 bytes and 32 components; no absolute paths, backslashes, controls, dot or empty segments. No actual file is discovered or opened.
• At most 2,000 total physical source lines, 500 pattern sections/lines, 5,000 supplied pairs/attribute tokens, 20,000 compiled glob tokens and 4,096 tokens per glob. Each query batch is refused before matching if its static dynamic-programming cost exceeds 2,000,000 cells. No pattern is compiled into a JavaScript regular expression.
• Configuration source uses LF/CRLF, no BOM/bare CR/prohibited controls, at most 8,192 characters per line. Matched source witnesses and property values are intentional output, so remove sensitive custom metadata before copying a report.
• A dedicated module Worker prepares the selected core before ready, with a 10-second preparation limit and a separate 2-second computation deadline. The result is a separate bounded JSON report; no editor, Git command, index, working-tree file, environment or server is accessed.
• Based on EditorConfig specification 0.17.2 for the declared subset: target paths and section globs are printable ASCII only. Glob tokens are literals/escapes, *, ?, complete ** path components, literal ASCII character classes with ! negation, and comma brace alternatives through 8 levels/128 expanded alternatives.
• Numeric brace ranges, unescaped class hyphen ranges, embedded **, nested/POSIX classes, non-ASCII globs/paths and single-arm nested braces are refused. A single-arm ordinary brace remains literal. These restrictions are explicit; this is not full EditorConfig core-test or every historical implementation conformance.
• Only preamble root=true/false affects traversal; the nearest supplied root=true stops higher supplied sources. Non-root preamble pairs are listed as ignored, while root under a section is refused. Later matching sections and closer files replace earlier keys; leading/trailing whitespace is trimmed and inline #/semicolon remains value data.
• All keys are lowercase. Standard property values are lowercase; custom value case is preserved. Literal unset removes a pair, including case-insensitive standard unset values. Empty and unknown/plugin-invalid values remain source strings. Keys/values are limited to 1,024/4,096 characters. No JSON value coercion, plugin validation, default tab width, derived indent_size, locale effect or editor file formatting is inferred.
• The formatted report is limited to 500,000 characters. Reduce the source when that output budget is exceeded.
• Inputs are processed on this device and are not automatically saved or uploaded.