Within a multi-root workplace and each root folder contains a .vscode/settings.json file, sqlfuff does not recognize any settings defined within when sqlfluff on a file within the associated root workplace.
Instead, sqlfluff appears to only recognize global user defined settings from User/settings.json
Each .settings.json file specifies settings such as path to the config file to use or the executablePath to use. None of these settings are utilized at runtime. No errors are returned. The extension simply uses the device global sqlfluff executable path and no .sqlfluff config file.
Within a multi-root workplace and each root folder contains a
.vscode/settings.jsonfile, sqlfuff does not recognize any settings defined within when sqlfluff on a file within the associated root workplace.Instead, sqlfluff appears to only recognize global user defined settings from
User/settings.jsonWorkspace Structure
|-- repo-1 | |-- .venv | | |-- bin | | | |-- sqlfluff | |-- .vscode | | |-- .settings.json | |-- sql | | |-- file_1.sql | | |-- file_2.sql | |-- .sqlfluff
|-- repo-2 | |-- .venv | | |-- bin | | | |-- sqlfluff | |-- .vscode | | |-- .settings.json | |-- sql | | |-- file_3.sql | | |-- file_4.sql | |-- .sqlfluff
A setting.json file could look like the following.
Each
.settings.jsonfile specifies settings such as path to the config file to use or the executablePath to use. None of these settings are utilized at runtime. No errors are returned. The extension simply uses the device global sqlfluff executable path and no .sqlfluff config file.