VSCode extension setting for config path(s)

[filiptibell]

When using a multi-root workspace we currently have to duplicate the same stylua.toml into each workspace root, it would be great to have a setting to point the VSCode extension to a config at the root of the repository instead.

A respective config for .styluaignore may also be necessary but I'm not sure if the CLI accepts a path arg for that?

[JohnnyMorganz]

I'm assuming the config file is present in some ancestor directory that both projects are part of?

This could probably be solved if we exposed --search-parent-directories as an option to configure in the extension

[filiptibell]

I'm assuming the config file is present in some ancestor directory that both projects are part of?

Yup, the full repo looks something like this:

packages/foo/...
packages/bar/...
packages/baz/...
stylua.toml

So just a pretty basic monorepo layout where most/all shared config should sit at the root, if possible.
Exposing --search-parent-directories would definitely solve this 👍🏻