posit-dev / posit-dev/positron

data explorer instance for non-top-level item does not update after editing (i.e. dataframe stored in a list)

Open
#10,892 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: data explorer bug support
Dominant language
TypeScript
Stars
4.3k
Forks
184
Avg merge
1d 9h
Merged PRs (30d)
195

Description

System details:

Positron and OS details:

Positron Version: 2025.11.0 build 234
Code - OSS Version: 1.105.0
Commit: 807acdfca108da6b9b2d96452fe047238da1bd9f
Date: 2025-10-31T23:02:00.803Z
Electron: 37.6.0
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Session details:

R 4.5.1

Describe the issue:

Data explorer tab is not updated after editing data in a list, even though the edits are reflected/visible in the session side panel under VALUES. Closing and reopening the data explorer tab solves the issue but not ideal to have to close and reopen the data explorer tabs after making any edits to the data.

Steps to reproduce the issue:

# make a dataset
set.seed(123)
n <- 10
dat <- data.frame(
  num_1 = rnorm(n),
  num_2 = rnorm(n, mean = 10, sd = 2),
  num_3 = rnorm(n, mean = 100, sd = 10)
)

# make a list of the dataset and 
# view dat_a from the list in data explorer (and keep the data explore tab open)
lst <- list(dat_a = dat, dat_b = dat, dat_c = dat)

# edit the dat_a in the list
lst$dat_a$num_4 <- rnorm(n, mean = 5463, sd = 764)

# go back to the same open data explorer tab; 
# the new column is not there (even though it is updated under VALUES in the session side panel). 

Expected or desired behavior:

Data explorer tabs should reflect the changes made to list elements. Basically, it would be super helpful to not have to close and reopen the data explorer tab(s) after making edits to data in lists, as in RStudio.

Were there any error messages in the UI, Output panel, or Developer Tools console?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the data explorer using the R list example in the report, then compare the open explorer tab with the session side panel's VALUES view after editing lst$dat_a. The work is done when an open data explorer tab reflects the new column without being closed and reopened.

Written by the indexing model from the issue text.

Assessment

Tech stack
r, typescript
Domain
data, desktop-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.