Make sess dependencies optional with an arf-backed transport
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 12/100
- Issue 類型
- 重構
- 描述清晰度
- 需要釐清
- 活躍度
- 活躍
- 技術堆疊
- r, rust, typescript
研究方向
This is an architecture proposal with no comments and no agreed scope, so it is not a starting point for a first contribution. Before any code, read the linked eitsupi/arf#112, #1739, #1829 and #1856 to see which transport boundaries are already decided. Done would be a maintainer-agreed design that separates the sess transport layer from its runtime functionality, with the dependency list for the arf-backed path settled.
由索引模型根據 Issue 內容生成。
描述
Motivation
vscode-R relies on the bundled sess package for session integration, including workspace inspection, viewers, and editor communication.
Although sess is now a pure R package, it still requires third-party dependencies such as processx, later, jsonlite, and rstudioapi.
These complicate installation, particularly in isolated environments managed by renv, pixi, etc.
PR #1856 improves installation isolation but does not eliminate these dependencies.
Meanwhile, arf already provides an IPC server implemented in Rust, potentially making much of sess's R-based communication infrastructure unnecessary.
Goal
Enable vscode-R session integration through arf without requiring third-party R packages.
This does not necessarily mean eliminating sess itself. Its pure-R runtime functionality could remain available while delegating communication to arf.
Ordinary R consoles and other frontends should continue using the existing sess transport.
Proposed direction
- Separate transport from runtime functionality. Reuse sess's existing workspace, viewer, and runtime integration logic across different transports.
- Use arf's IPC server. Extend its generic capabilities where necessary, particularly for structured R queries and event notifications, without introducing vscode-R-specific APIs.
- Make dependencies optional. Remove
processx,later, andjsonliterequirements from the arf-backed path, and makerstudioapiintegration optional. Existing uses outside the transport layer will also need attention. - Integrate incrementally. Start with ordinary arf terminals and subsequently consider R Interactive, reusing existing abstractions where appropriate.
Scope
This is a long-term architectural direction, not a proposal to replace sess entirely or remove support for other R frontends.
The goal is to reduce installation requirements without duplicating session functionality or compromising compatibility.
Related
- eitsupi/arf#112: Generic IPC server and earlier integration discussions
- #1739: Runtime and transport lifecycle separation
- #1829: Keeping sess a pure R package
- #1856: Managed sess installation
- 主要語言
- TypeScript
- 星號
- 1.2k
- 分支
- 151
- 平均合併
- 18 小時 28 分鐘
- 30 天內合併 PR
- 56
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
REditorSupport/vscode-R 的其他 Issue
-
[Bug]: indentation clash (formatter vs lintr)可能已有人在做 @renkun-ken 於 15 天前認領。 未關閉bug
難度 1/5 1 小時以內 新手友好度 92/100
REditorSupport/vscode-R#1883 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 68/100
REditorSupport/vscode-R#1846 · 2 則留言 ·
維護者通常 1 天內回覆
-
(feat) Additional Arrow support可能已有人在做 @Fred-Wu 於 20 天前認領。 未關閉enhancement
難度 2/5 1-3 小時 新手友好度 72/100
REditorSupport/vscode-R#1785 · 2 則留言 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 25/100
REditorSupport/vscode-R#1923 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 3/5 1-2 天 新手友好度 45/100
REditorSupport/vscode-R#1922 ·
維護者通常 1 天內回覆
查看 REditorSupport/vscode-R 的全部 Issue
相似的 Issue
-
needs-area-label
難度 2/5 1-3 小時 新手友好度 66/100
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
liberation-data/drivine#615 ·
維護者通常 1 天內回覆
-
backend bug ready-for-agent
難度 2/5 1-3 小時 新手友好度 78/100
geolens-io/geolens#3639 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 76/100
radius-project/ai-extensions#1196 ·
維護者通常 1 天內回覆
-
good first issue
難度 1/5 1-3 小時 新手友好度 88/100