REditorSupport / REditorSupport/vscode-R
Auto refresh/reload table viewer
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 139
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
Table viewer does not reload automatically when the dataframe or matrix being shown changes. It is somewhat cumbersome to have to close that view and re-open it in order to reflect changes. I apologize if this has already been discussed, but I couldn't find a related issue.
Describe the solution you'd like
Ideally, the view of the table will refresh/reload automatically when the dataframe or matrix being displayed is modified.
Describe alternatives you've considered
A somewhat "inelegant" alternative would be to just implement a keybinding or command that closes the view of an object foo and then immediately calls View(foo) again.
Additional context
Below is a recording of what I mean, hoping it helps to make my point more clear. The simple example code is
library(dplyr)
library(magrittr)
# Open table viewer for `df`
df <- starwars
View(df)
# Update `df`; problem is that changes are not reflected in viewer
df %<>%
filter(height < 100)
https://user-images.githubusercontent.com/9773292/155612306-407ac62f-29ef-40a4-abf3-40f894b79b5c.mov
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
Start with the table viewer entry point, using the R example with View(df) and a subsequent dataframe modification to reproduce the stale display. Trace how the viewer receives or renders the displayed object; done means an open viewer automatically reflects changes without closing and reopening it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, typescript, vscode
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100