Can we use the default host names?
- 主要語言
- TypeScript
- 星號
- 130
- 分支
- 48
- 平均合併
- 3 天 3 小時
- 30 天內合併 PR
- 15
描述
Having the set of host names generated by the CLI (`coder.`) and the set of host names generated by the plugin (`coder-vscode.--*`) causes some confusion when you mix connecting via the remote SSH plugin and connecting through our plugin.
Basically, you can get a different set of settings and recents, because VS Code thinks they are different connections (the host names are different, after all).
I believe we do this for two reasons:
1. So we can use `vscodessh` instead of `ssh`.
2. To attach an environment variable that allows us to track the connection as a VS Code connection, and not just a regular SSH connection. (Which, by the way, means that connections done with the remote SSH plugin without our plugin will not be tracked as VS Code connections!)
The first is easily solved, the JetBrains plugin already uses the regular `ssh` command. I think we just have to port the network info command? And this would make it usable with JetBrains as well, so win-win.
The second is trickier. We need some way to identify the connection but I am not sure how. We could track the process on the remote instead, like we do with JetBrains?
貢獻指南
研究方向
先追蹤 CLI 和 plugin 如何產生主機名稱,然後閱讀 JetBrains plugin 對一般 ssh 命令及其網路資訊命令的使用方式。當兩條連線路徑能夠共用預設主機名稱,同時仍能識別和追蹤 VS Code 連線時,這項工作就完成了。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- typescript
- 領域
- devtools
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 30/100