Feature request: Per-firectory or per-file environments

[SlashScreen]

Is there a way I could set files under a specific directory to use a @meta file as an environment? If not, how would I accomplish this? In my project, a certain folder as a number of modular scripts that have an environment separate to the rest of the project.

[tomlau10]

There are already a few similar feature requests and discussions:

• How to apply different libraries to different files? #2157
• Global in one file affects diagnostics in another #2340
• [Feature Request] Multiple-project/Monorepo support #2962
• How to "scope" definition file? #3030

The closest thing for supporting separate environment currently is using the multi-root workspace feature: https://luals.github.io/wiki/developing/#multiple-workspace-support
And vscode is one of the editors that support this feature.

[justarandomgeek]

i have recently found that doing local _ENV = _ENV --[[@as SomeClassToUseAsEnv]] at the top of a file kinda-sorta works to change the environment - the autocomplete is still only using the regular global environment, but the type checking applies the new class as env to tell you what globals are actually valid! (and i've been considering a small plugin hack to rewrite some special comment into this, but it doesn't quite work well enough for me to go down that road...)

(Notably though, doing ---@cast _ENV SomeClassToUseAsEnv instead seems to do nothing at all!)