Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't specify import map on a per workspace folder basis #726

Closed
khaled opened this issue Oct 5, 2022 · 1 comment
Closed

Can't specify import map on a per workspace folder basis #726

khaled opened this issue Oct 5, 2022 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@khaled
Copy link

khaled commented Oct 5, 2022

I've got a workspace with multiple root folders in it. They represent a couple different Deno projects, a couple of Node projects, and some other non-JS projects. The Deno projects have different, separate import maps, yet I am unable to specify an import map at the folder level. Only the following settings are available:

Screen Shot 2022-10-05 at 1 35 52 PM

It appears to be possible to set import map only at the workspace level.

To Reproduce

  1. Create a workspace and add multiple root Deno folders to it.
  2. Go into VS code settings and select one of the folders
  3. Look at Deno settings.

Expected behavior

I can set import maps at the root folder level.

Versions

vscode: 1.68.1 deno: 1.25.4 extension: 3.13.1

@khaled khaled changed the title Can't specify import map on a per workspace folde rbasis Can't specify import map on a per workspace folder basis Oct 5, 2022
@kitsonk kitsonk added the duplicate This issue or pull request already exists label Oct 5, 2022
@kitsonk
Copy link
Contributor

kitsonk commented Oct 6, 2022

At a fundamental level this is a duplicate of denoland/deno#14245. It is a design limitation in that there is one configuration per running language server, and there is only one running language server per workspace, and the referenced issue would make varying the active configuration per workspace folder possible. Challenge is it is not a small piece of work.

@kitsonk kitsonk closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants