eclipse-theia/theia

[vscode] Running example FileSystemProvider plugin has different behavior

Open

#8,167 创建于 2020年7月14日

在 GitHub 查看
 (9 评论) (0 反应) (0 负责人)TypeScript (18,676 star) (2,478 fork)batch import
bughelp wantedvscodeworkspace

描述

Bug Description:

When trying to use example FileSystemProvider plugin the (expected) behavior on Code[1] differs from the behavior on Theia[2].

[1] Running plugin command Setup workspace with or without opened workspace creates new and empty directory with name that was passed to vscode.workspace.updateWorkspaceFolders in extension.ts. image

[2] Running plugin command Setup workspace without opened workspace throws an error Failed to update workspace folders: Error: There is not active workspace. If any folder was already opened in the workspace, the same plugin command opens new directory, but instead of named, empty one it's system's root. image

Steps to Reproduce:

  1. Clone microsoft/vscode-extension-samples
  2. Add fsprovider-sample plugin to Theia
  3. Run Theia
  4. Execute Setup workspace command from the command paletter

Additional Information

  • Operating System: Ubuntu 18.04 if running on Docker image Arch Linux, kernel 5.7.7 if running on host
  • Theia Version: Tried both release 1.3.0 and compiling akosyakov/integrate-vscode-api-7269 branch.

贡献者指南

技术栈
typescript
领域
backendtoolingdesktop
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
TypeScriptVS Code extension APITheia plugin systemGit
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate the difference in workspace folder handling between VS Code and Theia by examining the FileSystemProvider sample and Theia's implementation of `vscode.workspace.updateWorkspaceFolders`. Look at the Theia source code, possibly in `packages/plugin ext` or related areas, to understand how workspace folders are managed. The issue references a branch `akosyakov/integrate vscode api 7269` which may contain relevant changes. Check the comments for any additional maintainer guidance.