Creating config files
You can seed a config file from your current VS Code UI settings with one command. Open the Command Palette and run either of the following:GLua: Create Linter Config File(creates.glua.json)GLua: Create Formatter Config File(creates.gluafmtrc.json)
Linter config (.glua.json)
Use .glua.json to define globals, diagnostic severity, and per-path overrides.
globals: declare addon names or libraries that are available at runtime but not defined in your workspace.diagnostics: set any rule to"off","warning", or"error".overrides: apply different rules to specific paths. In the example, vendored files underlua/vendor/**do not report unused locals.
Formatter config (.gluafmtrc.json)
Use .gluafmtrc.json to control indentation, line width, quotes, and block collapsing.
useTabs: indent with tabs instead of spaces.indentSize: number of spaces per indent level (ignored whenuseTabsis true).maxLineWidth: soft wrap target for long lines.quoteStyle:"double"or"single"for string literals.keepSingleLineBlocks: preserve one-lineifblocks instead of forcing expansion.overrides: change formatting per path. In the example, files underlua/config/**use two-space indentation.
Both
.glua.json and .gluafmtrc.json ship with bundled JSON schemas, so you get IntelliSense and validation while editing them in VS Code.