EditorConfig by Bitno
A lightweight, private and secure EditorConfig for VS Code, made for monorepos.
Early development: this extension is still being built. Expect missing features, rough edges and breaking changes between versions.
Lightweight, private and secure by design
Built by a developer, for developers, from Serbia. Free to use, with no paid tier.
- Lightweight: No language server. It reads your
.editorconfig files only when you open or save a file.
- Private: No telemetry, no account, no network. It reads only your
.editorconfig files and open documents.
- Secure: It runs nothing it reads, and changes a file only when you save it.
Applies your style
- Indentation:
indent_style, indent_size and tab_width set each editor's tabs or spaces and their width, as soon as it opens.
- On save:
trim_trailing_whitespace trims the ends of lines, insert_final_newline ends the file with a newline, and end_of_line sets lf or crlf. On an auto save, the line you're typing on keeps its trailing spaces.
Made for monorepos
- Package by package: each folder's
.editorconfig applies on top of the ones above it, until one says root = true.
- Always current: change any
.editorconfig, in any package or workspace folder, and the open editors it affects follow at once, without reopening them.
- Where each value comes from: run EditorConfig: Show the Properties of This File to see every property that applies, with the file and section that set it; pick one to go there.
- Linked files: above each
.editorconfig, links to the ones it applies on top of, or a note that root = true stops the lookup there.
Edits .editorconfig files
- Syntax colors for sections, globs, keys and values.
- Checks: lines no tool can read, values a property doesn't accept,
root in a section, and keys set twice in one section. Keys other tools define, such as ij_ keys, are left alone.
- Completion of the specification's properties and their values, and hover with what each property does.
Feedback
Found a bug, or missing something? Open an issue. Questions and ideas go to Discussions. Blunt feedback is welcome.
| |