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

Filtering not working properly #93

Open
nealhaddaway opened this issue Apr 27, 2022 · 7 comments
Open

Filtering not working properly #93

nealhaddaway opened this issue Apr 27, 2022 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@nealhaddaway
Copy link
Contributor

Filtering isn't working properly (see Jacqui's email example)

@nealhaddaway nealhaddaway added the bug Something isn't working label Apr 27, 2022
@DrMattG
Copy link
Collaborator

DrMattG commented Apr 28, 2022

Weird error alert!
If I download the filtered data from the App I get the correct dataframe - so it has to be something to do with the data_active reactive values.... I just cant see what it is. Confused.....

@nealhaddaway
Copy link
Contributor Author

nealhaddaway commented Apr 28, 2022 via email

@afeierman
Copy link
Collaborator

Displaying filtered datasets around the app was definitely tricky. I think the ultimate solution was kind of a patch once we had the finished app, so it might be easier to scrap a few sections and start over. There is a toggle that should switch between showing the filtered dataset or not on each tab, but it might be buggy. @DrMattG if you find a more specific section of code you have questions about tag me and I'm happy to elaborate on anything

@DrMattG
Copy link
Collaborator

DrMattG commented May 3, 2022

Thanks @afeierman - the problem is in this section here:

data_active <- reactive({

if I comment out the dataset_gateway part then filtering works
`
data_active <- reactive({
req(data_internal$raw)

  #dataset_gateway <- (!is.null(input$map_filtered_select))

  d_out <- #if (dataset_gateway && input$map_filtered_select == TRUE) {
    data_internal$filtered
  #} else {
   # data_internal$raw
  #}

   d_out

`

So I guess it has got something to do with the map_filtered button but I am not sure yet what that is!

@DrMattG
Copy link
Collaborator

DrMattG commented May 4, 2022

This doesnt fix the bug but in #96 I have seen it is to do with the order in which the user clicks on the tabs - clicking on the atlas first allows the filtering. Clicking on the datatable first does not......

If the user goes from upload to map to datatable then the data_gateway is TRUE (allows filter)
If the user goes from upload to datatable then the data_gateway is FALSE (doesnt allow filter)

(I am just documenting my thoughts and ramblings!)

@DrMattG
Copy link
Collaborator

DrMattG commented May 16, 2022

Remove filtering @DrMattG

@DrMattG
Copy link
Collaborator

DrMattG commented May 17, 2022

I've taken the filters out (just commented out the code for the moment) in PR #101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants