You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In certain scenarios when using multi-root workspaces in vscode a Deno configuration file is not being auto detected (see: denoland/fresh#514).
We should better determine which root to auto detect a configuration file, by enumerating the workspace folders checking their enablement and seeing if there is a config file, until one is found.
We might also want to consider logging out the path searched for a configuration files, wether we find them or not, as we currently only log when we find one, making it difficult to identify why somethings isn't working.
Currently it's by design that we only look at the first workspace folder, auto-detection in other places only makes sense coupled with multi-config monorepo support. Tracked by denoland/vscode_deno#787 and #14245.
In certain scenarios when using multi-root workspaces in vscode a Deno configuration file is not being auto detected (see: denoland/fresh#514).
We should better determine which root to auto detect a configuration file, by enumerating the workspace folders checking their enablement and seeing if there is a config file, until one is found.
We might also want to consider logging out the path searched for a configuration files, wether we find them or not, as we currently only log when we find one, making it difficult to identify why somethings isn't working.
Ref #14455 - re-working workspace folders
The text was updated successfully, but these errors were encountered: