Setting up `codestyle-check` precisely?

Nessuno ha ancora preso questa issue.

Hi there!

Is there any way to set up (disable) exact checks for `codestyle-check`?
`.stylua.toml` and `.editorconfig` syntax doesn't have much parameters, and doesn't cover such usecases like "spaces before single argument".

For example, when I type `local a = require"foo".moo`, and I don't want that codestyle checker triggered on missing space (or anything) here, and I want this "globally" (to don't place comments `---@diagnostic` comments here and there and everywhere everytime).

Or, say, I have function, that takes a table as argument, and place `table` global in metadate, to allow OOP-like calls on tables.

So, as syntactig sugar I have variable `T` set to this function.
So, I'm initializing tables with `local mytable = T{}`.

And I don't want that codestyle-checker blame on missing space here too.

And so on...

So, it would be nice, if there was a possibility to configure (enable/disable) exact checks per-project **and** globally (default settings, that per-project ones would override).

And I digged all around lua_ls and emmylua docs and didn't find a way to do that.

Can you advice me, please?

Inizia verificando come codestyle-check sia collegato a .stylua.toml e .editorconfig, quindi consulta la documentazione di lua_ls ed emmylua menzionata nell'issue. Una modifica completa definirebbe impostazioni a livello di progetto e globali per abilitare o disabilitare singoli controlli, con le impostazioni del progetto che sovrascrivono i valori predefiniti.

Scritto dal modello di indicizzazione a partire dal testo della issue.