Closed dsen6644 closed 8 months ago
Hi,
the solution for explicitly calling the _open input value adds much complexity when working in a modular workflow.
I'm not sure to understand, in a module you can use input$select_open
like you use input$select
, why do you need this here ?
I 'll take a look if it's possible to send input vlaue after close rather than on change.
virtualSelectInput()
now has an updateOn = "change" or "close"
argument.
Works perfectly, thank you!!
Complete
While this has been requested before (#392), the solution for explicitly calling the
_open
input value adds much complexity when working in a modular workflow.Below I have a sample app that chains reactivity between modules so that updates in the pickers higher up in the hierarchy will dynamically limit the number of options available in subsequent pickers.
Because the inputs are being generated through namespaces it becomes difficult to 'explicitly' call the
_open
id.