REditorSupport / REditorSupport/vscode-R
Any plan for further improvement and development
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 139
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 5
Description
There have been no activity in the past 6 months, just would like to check any future plan for vscode-R?
I guess it is mature to some extend, and I have been using it in daily basis in the past 2 years.
It would be a pity if it ends like this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points and does not define a concrete change. Read the issue and its discussion first, then identify whether maintainers want a specific improvement for vscode-R; a suitable follow-up would need a scoped target and an explicit completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100