Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When filtering tibble inside DataViewer and clicking into a nested list item for details, results show non-filtered tibble’s list value at this position instead of currently filtered/selected row's list value #7546

Closed
rweberc opened this issue Aug 7, 2020 · 6 comments

Comments

@rweberc
Copy link

@rweberc rweberc commented Aug 7, 2020

Where is the bug?

Data Viewer in RStudio

Describe the problem in detail

When using the "magnifying glass" tool in DataViewer to look at a nested list in a tibble that has been filtered within the DataViewer, the value that is shown corresponds to the non-filtered row at the position selected, rather than the currently selected row's value.

Steps to reproduce the problem

  1. Run the following:
df <- dplyr::tribble(
  ~ id, ~ val,
  "1", list(1, 2, 3),
  "2", list(4, 5, 6),
  "3", list(7, 8, 9)
) 

View(df)
  1. In Data Viewer, filter to id equals 3:

image

  1. Click the magnifying glass in the 'val' cell (next to list(7, 8, 9)).

  2. Values displayed for df[[2]][[1]] of the unfiltered data frame (list(1, 2, 3)) rather than list(7, 8, 9) as expected from the specific cell clicked on:

image

Environment

R Version: 3.6.1
Dplyr: 1.0.1
RStudio Desktop (Version: 1.3.1056)
Windows 10

R Version: 3.6.1
Dplyr: 0.8.5
RStudio Desktop (Version: 1.2.5019)
Windows 10 Version 1803
@rweberc rweberc changed the title Selecting a nested list item in a filtered DataViewer data set results in non-filtered data set row's list value being shown instead of currently selected row's list value When filtering tibble inside DataViewer and clicking into a nested list item for details, results show non-filtered tibble’s list value instead of currently filtered row's list value Aug 10, 2020
@rweberc rweberc changed the title When filtering tibble inside DataViewer and clicking into a nested list item for details, results show non-filtered tibble’s list value instead of currently filtered row's list value When filtering tibble inside DataViewer and clicking into a nested list item for details, results show non-filtered tibble’s list value at this position instead of currently filtered/selected row's list value Aug 10, 2020
@ronblum
Copy link
Contributor

@ronblum ronblum commented Aug 10, 2020

@rweberc Thank you for filing this. I can reproduce this in RStudio Desktop 1.4.673, as well. We'll review the bug as we continue developing RStudio.

@stale
Copy link

@stale stale bot commented Feb 5, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, per https://github.com/rstudio/rstudio/wiki/Issue-Grooming. Thank you for your contributions.

@stale stale bot added the stale Issues which have been closed automatically due to inactivitiy. label Feb 5, 2021
@stale
Copy link

@stale stale bot commented Feb 19, 2021

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Feb 19, 2021
@noahatchison
Copy link

@noahatchison noahatchison commented Aug 19, 2021

This issue still exists in the following environment:

R Version: 4.1.0
dplyr: 1.0.7
RStudio Desktop: 1.4.1717
Windows 10: 19043

@ronblum
Copy link
Contributor

@ronblum ronblum commented Aug 19, 2021

Reproduced in

  • RStudio Desktop 2021-08.0.317 on MacOS 12 beta
  • RStudio Server 2021-08.0.317 via Safari on MacOS 12 beta

@ronblum ronblum reopened this Aug 19, 2021
@stale stale bot removed the stale Issues which have been closed automatically due to inactivitiy. label Aug 19, 2021
@ronblum ronblum added this to the Elsbeth Geranium (2022-03.0) milestone Aug 19, 2021
@jgutman
Copy link
Contributor

@jgutman jgutman commented Jan 13, 2022

This is a duplicate of #9960 -- will address the issue there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants