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

No support for folder-specific settings in Multi Root Workspaces #242

Open
hblanko opened this issue Aug 16, 2022 · 0 comments
Open

No support for folder-specific settings in Multi Root Workspaces #242

hblanko opened this issue Aug 16, 2022 · 0 comments
Labels

Comments

@hblanko
Copy link

hblanko commented Aug 16, 2022

Describe the bug

Currently, the Multi Root Workspace API doesn't seem to be supported by the extension.

If a workspace contains several root folders, VS Code allows configuring specific settings for each of them: this is called a Multi Root Workspace setup. However, autoDocstring is unable to recognize this structure, only allowing for settings to be at workspace or higher levels. When configuring an autoDocstring setting at workspace folder level, it becomes grayed out indicating that "This setting cannot be applied in this workspace. It will be applied when you open the containing workspace folder directly.", just as explained in the documentation if the feature is not supported.

image

Versions:

  • autoDocstring Version: 0.6.1
  • Operating System: GNU/Linux 5.15.0-46-generic (Ubuntu 22.04) x86_64
  • Vscode Version: 1.70.1

Expected Result:

autoDocstring generates docstring following the specific workspace folder settings.

Actual Result:

autoDocstring dismisses workspace folder settings and directly takes higher level settings (user, workspace).

Additional context

Microsoft provides a guideline on how to adapt VS Code extensions to support the Multi Root Workspace API.

@hblanko hblanko added the bug label Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant